Multitech FF240 ユーザーズマニュアル
Multi-Tech Systems, Inc.
FF240-IP Admin User Guide
95
Appendix B – Customization
Web Services API
Introduction
This section illustrates the HTTP/XML communication between the FF240-IP Web Service (FFWS) and a
client. FFWS provides an interface to the FF240-IP units for client applications. Client applications can
use FFWS for sending faxes, managing contacts and monitoring fax status.
client. FFWS provides an interface to the FF240-IP units for client applications. Client applications can
use FFWS for sending faxes, managing contacts and monitoring fax status.
Authorization
All request requiring authorization must have the Authorization header set using Basic authentication. If
this is not set or the username or password are incorrect then “401 Unauthorized” is returned.
this is not set or the username or password are incorrect then “401 Unauthorized” is returned.
See RFC 2617 for implementation
HTTPS
The server supports HTTPS. Secure requests can be sent to the default HTTPS port 443.
Creating a new fax
An application can schedule a fax by posting the schedule fax XML to the ofax resource. If the fax is
successfully scheduled then a response is returned with the scheduled entries.
successfully scheduled then a response is returned with the scheduled entries.
Each file that you wish to attach as fax pages must be placed in an attachment element. An "inline"
attachment is an attachment with the contents of the file inserted into the content tag. Inline
attachments must be encoded using base64. The name of the attachment can usually be set to the
basename of the file unless that name is not unique among the attachments. The name is used primarily
for error responses, so if you would like to know the attachment which failed then it is important to
make this field unique. The content type of the attachment should be set to match the type of file being
transferred. For example, if you are attaching a PDF, then the content type should be set to
"application/pdf". It is important to properly set the type because this field is used when converting the
file into fax pages. No attempt is made to guess the content type on the server.
attachment is an attachment with the contents of the file inserted into the content tag. Inline
attachments must be encoded using base64. The name of the attachment can usually be set to the
basename of the file unless that name is not unique among the attachments. The name is used primarily
for error responses, so if you would like to know the attachment which failed then it is important to
make this field unique. The content type of the attachment should be set to match the type of file being
transferred. For example, if you are attaching a PDF, then the content type should be set to
"application/pdf". It is important to properly set the type because this field is used when converting the
file into fax pages. No attempt is made to guess the content type on the server.
Limits
Request size: 2MB for [12]30, 5MB for [48]30
Maximum Recipients per Fax: 400
Maximum Recipients per Fax: 400
Query Parameters:
None
HTTP Request line:
POST /ffws/v1/ofax HTTP/1.1
HTTP Response Status Codes:
201 Created
The fax has been created successfully.
400 Bad Request
Invalid request. The fax has not been scheduled. A more verbose message may
be provided in the response message if possible.
400 Bad Request
Invalid request. The fax has not been scheduled. A more verbose message may
be provided in the response message if possible.