3.18.0
The Followup WorkOrder REST API Interface defines the REST API interface which customers will need to implement if they would like ServiceMobility to book a follow-up work order via their own systems.
By implementing an API which matches the Followup WorkOrder REST API Interface, customers can configure ServiceMobility (via the Entity System Configuration object) so that requests to book a follow-up work order via the Book Job REST API are passed through to their system.
Before being able to book a follow-up work order via their own systems, customers will also need to implement the REST Interfaces Appointment Search, so that the Appointment Search REST API will search open appointment slots via their own systems first, so that a slot can be selected, and then booked.
On this page:
Related pages:
Resource URL Summary
Request to book a new work order for the specified time slot
POST <REST Endpoint URI>
API Specific Parameters
| Parameter | Description |
|---|---|
| ServiceMobility with replace the text
|
It is mandatory for the REST Endpoint URI to contain the text HTTP Headers
ServiceMobility will set both of the Standard HTTP Headers when calling this REST API Interface.
That is:
- The
Content-Typeheader will be set toapplication/json; and - The
x-access-tokenheader will be set to the JWT that was used in the call to the API that triggered ServiceMobility to call the configured endpoint that implements this interface.
The x-access-token header will either be the JWT issued by ServiceMobility, or by the endpoint that implements the Authentication REST API Interface that ServiceMobility has been configured to use.
Implementations of this interface may evaluate the JWT supplied, if required, but please note that ServiceMobility will have already authenticated the JWT in the initial API call before passing the call on to the configured endpoint.
API Specifics
Request to book a new work order for the specified time slot
This REST API must request the booking of a new Work Order for an available appointment slot that has been obtained via the Appointment Search REST API, using the REST Interfaces Appointment Search.
URL
POST <REST Endpoint URI>
HTTP Request Body
The HTTP request body will contain a valid REST Object Definitions Work Order Activity Related Objects Book Job Object.
HTTP Response
Response Codes
| HTTP Code | Description |
|---|---|
| 200 | OK. The IVR message was sent successfully. |
| 401 | Invalid Logon. |
| 500 | Server error. An error occurred while processing the request. The HTTP response body should have more details as to the possible cause. |
On success, an HTTP response code of 200 must be returned, and the response body must contain a valid response body that is the same as would be returned from the Book Job REST API.
ServiceMobility will return the response code (and response body, if present) as the response to the initiating Book Job REST API call.