The Travtus Messaging API allows clients and partners to interact with Travtus Teammates via their own phone number routing or web chat solutions. Follow the instructions below to set up and use the Messaging API.
To use the Messaging API, request API credentials by contacting our support team at [email protected].
The following users and systems are involved in this integration scenario:
All API requests must be authenticated using the provided API credentials.
The following step-by-step description provides a detailed explanation of the logic and API requests used at each step of the workflow.
The customer sends a message via the Source System (e.g., SMS, web chat).
If the customer conversation does not yet have an existing session, the Source System creates a new session for the customer by sending a request to the Travtus Messaging API.
Upon receipt of the “create session” request, the Travtus Messaging API will create a new session, returning a 200 status with the sessionId
and userId
.
Once a customer session is created, customer messages can be submitted.
The Source System sends the message data to the Travtus Messaging API to create a message in the Travtus system using the supplied sessionId
.
Upon receipt of the “message” request, the Travtus Messaging API adds a new message to the conversation, returning a 200 status.
In case of an expired session, a session_not_found
error is returned.
Travtus API replies are sent to the appropriate webhook:
Webhook calls expect to receive an HTTP 200 status response.
Participant types:
bot
: Travtus Teammateagent
: Human agentCommon error responses:
API rate limits are imposed to ensure fair use. Please contact support for details on rate limits.
To receive responses from the Travtus API, set up a webhook by sending a request to the following endpoint:
The Travtus Messaging API allows clients and partners to interact with Travtus Teammates via their own phone number routing or web chat solutions. Follow the instructions below to set up and use the Messaging API.
To use the Messaging API, request API credentials by contacting our support team at [email protected].
The following users and systems are involved in this integration scenario:
All API requests must be authenticated using the provided API credentials.
The following step-by-step description provides a detailed explanation of the logic and API requests used at each step of the workflow.
The customer sends a message via the Source System (e.g., SMS, web chat).
If the customer conversation does not yet have an existing session, the Source System creates a new session for the customer by sending a request to the Travtus Messaging API.
Upon receipt of the “create session” request, the Travtus Messaging API will create a new session, returning a 200 status with the sessionId
and userId
.
Once a customer session is created, customer messages can be submitted.
The Source System sends the message data to the Travtus Messaging API to create a message in the Travtus system using the supplied sessionId
.
Upon receipt of the “message” request, the Travtus Messaging API adds a new message to the conversation, returning a 200 status.
In case of an expired session, a session_not_found
error is returned.
Travtus API replies are sent to the appropriate webhook:
Webhook calls expect to receive an HTTP 200 status response.
Participant types:
bot
: Travtus Teammateagent
: Human agentCommon error responses:
API rate limits are imposed to ensure fair use. Please contact support for details on rate limits.
To receive responses from the Travtus API, set up a webhook by sending a request to the following endpoint: