Skip to content

Http Headers

HTTP headers are the name or value pairs that are displayed in the request and response messages of message headers for Hypertext Transfer Protocol (HTTP).

Usually, the header name and the value are separated by a single colon. HTTP headers are an integral part of HTTP requests and responses.

Message Tracking

Travlinq API supports echo tokens based on Http headers for every operation for diagnosis and tracking purposes. The Description and recommended usage of each token are as follows.

Token Name HTTP Header Recommended usage
Conversation Identifier(CID)* conversationId A unique identifier for identifying set of messages used for performing an operation (Search and Book ).
This needs to be generated by integrator end and it needs to be sent with each operation request header in a given search and booking flow. This will allow only below charters and it should be generated with UUID standard.
a75f2ed1-00cd-4d85-aeff-4f0ba97ddaa2
The conversationId is optional for loging API call . But after that it is mandatory to have conversationId with all subsequent requests.
Retrieve Identifier* retriveId A unique identifier for identifying a given messages used for performing an operation (Search to Book ).
This is generated from back end per each response and it is available only with response headers.
Session Identifier(token)* sessionId A unique identifier for user session .You'll need to include an access token(sessionId) in every request that you make to the API.
The access token can be generated from Auth service by using client account. The accesses token will be valid only for 6 hour(Duration is configurable).
After token is expired user has to regenerate and use new token for following API calls. When token is expired user will get VAL-002 error code.

Consumers can set these identifiers as per their requirements and Travlinq API will echo these values back with the responses. Also these values are being logged at the service side so that they can be used for troubleshooting purposes.

Conversation Id

This has to be generated(UUID) by integrating user end, and it has to be pass with each API call during each operation in Search to Booking flow. It should be sent as HTTP Header parameter . The conversationId is unique for any given search to book flow. When user will make a new search then user has to generate a new conversationId when logging to the system. Then it needs to be sent with each API call in the same flow search to booking . The conversationId format will only allow below charters.
a75f2ed1-00cd-4d85-aeff-4f0ba97ddaa2

X-API-KEY

You'll need to include an API access key(X-API-KEY) in every request that you make to the API. The access token can be taken from Travlinq support team.

Http Request Headers

In order to access our API, you will need to pass the following two http headers for each call.

  • sessionid: 8c02f3bb-664d-40e3-81b2-4544e9585323"

  • conversationid: 6970334c-1a0a-4668-a4c5-77d7f1cb6709"

  • X-API-KEY: VxjYmSYcRfageSkehwiPe5i7IsY2LXBka7hQ8jZi

Http Response Headers

  • sessionid: 8c02f3bb-664d-40e3-81b2-4544e9585323"

  • conversationid: 6970334c-1a0a-4668-a4c5-77d7f1cb6709"

  • retriveId: f9cddbfd-0b30-4999-bb6e-d364e5b63fe2"