Definitions
BulkJobReportResponseBody
Name | Schema |
---|---|
reports | < BulkJobReportResponseBodyItem > array |
BulkJobReportResponseBodyItem
Name | Description | Schema |
---|---|---|
deleted | Information on whether the job report could be deleted. Only present for responses to a bulk DELETE. | boolean |
jobId | The Job ID. | string |
pages | Number of pages in the fax. Only present for responses to a bulk GET. | integer |
reason | Missing if deletion was successful, otherwise one of the following reason messages is returned:
| boolean |
recipientStatus | Fax recipient and status information. Only present for responses to a bulk GET. | <FaxRecipientWithStatus> array |
reference | Only present for responses to a bulk GET. |
BulkJobReportsRequestBody
Name | Description | Schema |
---|---|---|
action | Defines the action to be performed on all jobs whose Job ID is provided in the Possible options are:
| string |
jobIds | List of Job IDs to be processed in bulk | < string > array |
DocumentWithData
Data and additional information on sent documents. If there is no document data and no cover page, the Webservice will not accept the job.
Either reference
or data
can be used in a single document, but not both at the same time.
Name | Description | Schema |
charset | Character encoding of plain text documents (*.txt). Possible values:
| string |
data | base64 string with data, if no reference is provided. If both are provided, the reference data (see above) is used. Example : "SGVsbG8sIHRoaXMgaXMgYSB0ZXN0aW5nIGRvY3VtZW50IGJvZHkgY 3JlYXRlZCBmb3IgOTk5OTlURQ==" | string |
name | Document file name. The file extension is important for determining the file type, e.g., Invoice-2017-01.pdf. The maximum possible length of a file name is 32 characters. Allowed characters are: a-zA-Z0-9-_., and no whitespaces, slashes, or other special characters are permitted. Example | string |
reference | A URL pointing to the document to be transmitted. Example | string |
FaxJobRequest
Name | Schema |
---|---|
documents | <DocumentWithData> array |
meta | |
recipients | < FaxRecipient > array |
reference | |
renderingOptions | |
statusReportOptions | |
transportOptions |
FaxJobResponse
Name | Schema |
---|---|
jobId | string |
FaxRecipient
If a fax can be successfully sent to the recipient fax number, the transmission is completed and considered successful. The destination number which received the fax will be indicated in the report data for each recipient under RecipientStatus - sentToNumber.
Name | Description | Schema |
---|---|---|
number | Dialed number (international format, e.g., +12015551000). Example | string |
properties | Personalized data for the cover page. | <RecipientProperty> array |
FaxRecipientWithStatus
Name | Description | Schema |
---|---|---|
durationInSecs | Duration of the fax transmission until received by the fax recipient. | integer |
number | The fax recipient’s primary number (international format, e.g., +49891234678). | string |
properties | Personalized data used for the cover page. | <RecipientProperty> array |
reason | Explanation of the status. | string |
remoteCsid | Fax ID, which identifies the fax recipient. | string |
sentToNumber | Number to which the fax was sent. | string |
sentTs | Timestamp indicates when the fax was sent (in ISO 8601 format). | string (date-time) |
status | Job status. See Transmission status codes - Outbound Fax for details. | string |
FaxReport
Name | Description | Schema |
---|---|---|
jobId | The Job ID. | string |
pages |
Number of pages in the fax. | integer |
recipientStatus |
| <FaxRecipientWithStatus> array |
reference |
|
FaxReports
Name | Schema |
---|---|
reports | <FaxReport> array |
HttpStatusPush
To receive notification via HTTP, the JobRequest must contain the httpStatusPush
element. The URL to which the HTTP POST request is sent has to be specified.
See HTTP status push for additional details.
Name | Description | Schema |
---|---|---|
authMethod | Authentication method. Possible values are:
| string |
credentials | The credential for the principal/username. Example | string |
principal | The principal/user name. Example | string |
targetUrl | Push URL. Example | string |
JobDeleteReport
Name | Description | Schema |
---|---|---|
deleted | Returns | boolean |
jobId | The Job ID. | string |
reason | Missing if deletion was successful. Otherwise, one of the following reason messages is returned:
| string |
JobValid
Contains a fax job's valid start/end (in ISO 8601 format). If this data is not defined correctly, you will receive a Job Expiration error (HTTP status code 400).
If you want to use the default values, simply ignore this object.
Name | Description | Schema |
---|---|---|
end | End of validity for the job (in ISO 8601 format). Durations are also supported. The following values are all valid expiration times:
By default, jobs expire one month after they begin being valid. | string (date-time) |
start | Beginning of validity for the job (in ISO 8601 format). If this time is not defined correctly, you will receive a Job Expiration error. Example values are "Z" for UTC or -05:00 for EST. By default, jobs are immediately valid. | string (date-time) |
MetaData
Meta information about the request.
Name | Description | Schema |
customerRefe rence required | Information that the customer can use for internal references. Example : "99999TE" |
string |
jobValid optional |
|
Overlay
Settings for the overlay (e.g., stationery). A template (e.g., with a letter header and footer) can be applied to all or specific pages in the fax. A template consists of a one-page, black-and-white document. In order to install an overlay, the customer transfers a template to Retarus, which is then saved in Retarus' infrastructure under a mutually agreed-upon name.
Name | Description | Schema |
---|---|---|
mode
| Specifies the page in the document where the template (overlay) will be applied. Possible values:
| string
|
name | Template name, without the path information and file extension. Example | string |
RecipientProperty
A cover page can be personalized for each individual recipient and then attached to the front of each fax document.
This object allows specifying a value for each of the keys in the template.
See Cover page personalization for additional information.
Name | Description | Schema |
---|---|---|
key | Name of the key. Example | string |
value | The value assigned to the key. Example | string |
Reference
Name | Description | Schema |
---|---|---|
billingCode | Information on the cost center; the format is arbitrary (max. 80 characters). Example | string |
billingInfo | Additional data for internal customer accounting (max. 80 characters). Example | string |
customerDefinedId optional | Freely-defined ID string (max. 256 characters). Example | string |
RenderingOptions
Contains instructions for the rendering of the fax.
Name | Description | Schema |
---|---|---|
coverpageTemplate | The name of the cover page’s template; e.g., coverpage- default.ftl.html. If an empty string is used, no coverpage will be applied, even if a default coverpage is set in EAS. Example | string |
header | The content of the header, including control characters. Example | string |
overlay |
| |
paperFormat | The size of the paper. Possible options are:
| string |
resolution | The fax’s resolution. Possible values are:
| string |
ReportMail
In addition to querying via Webservice, requesting notification for each fax job is possible as soon as processing is completed. The status information can be sent by either HTTP POST or email. Separate email addresses can each be specified for delivery and failed delivery confirmations. If an email address is deleted for either type of confirmation, no notification email will be sent for the confirmation type that was removed.
The report emails' format is specified through a template that is filled out with relevant data (Job ID, job status, details on the fax recipients). A default template is available for all customers; however, you can install a customized template. Templates must be encoded in UTF-8 format. In addition, it is possible to specify whether the fax image should be attached to the report or not and, if so, in which format.
Name | Description | Schema |
---|---|---|
attachedFaxImageFormat optional | Determines when the fax image will be attached to the email. The following formats are supported:
| string |
attachedFaxImageMode optional | Determines when the fax image will be attached to the email. Possible values are:
| string |
failureAddress | Email address to which a notification should be sent when errors occur. Example | string |
successAddress | Email address to which delivery confirmation notifications should be sent. Example | string |
StatusReportOptions
Settings for the status report. Consists of reportPurgeTs
and reportMail
.
Name | Description | Schema |
---|---|---|
httpStatusPush |
| |
reportMail |
| |
reportPurgeTs | Not currently valid. The date after which the status report is no longer available. In ISO 8601 format Example | string (date-time) |
TransportOptions
Contains information on the transmission of the fax.
Name | Description | Schema |
---|---|---|
csid | The sender ID that is displayed to the recipient of the fax. (max. 20 characters). Example | string |
isBlacklistEnabled | Flag for the use of the Robinson List (only for numbers in Germany), ECOFAX (for numbers in France), or Retarus' own blocklist. | boolean |
isExpress | Flag for transmissions sent express. | boolean |