Headers

Some special headers that could make your quality of life easier.

Request Headers
Header
Description
Accept-Language
This conforms to the regular HTTP specification for language but if the supplier has translated their content it will return the content in the specified language if possible. Also all error messages will be translated. eg. Accept-Language: fr the server will then respond with Language: fr depending on if that language was available.
Octo-Env
This header will mark any booking you perform with live credentials as a test sale. This will mean it will not consume any availability, the barcodes will not work, and you will not be invoiced for it. e.g. Octo-Env: test and to turn it off, change the value to live.
Content-Type
This must be application/json for all POST PATCH and DELETE requests.
Referer
This is only used with checkout connections but allows a sale to be associated to a reseller using their referer.
Response Headers
Header
Description
Octo-Capabilities
A list of the capabilities that were initialised with this request.
e.g. Octo-Capabilities: octo/pricing, octo/content
Octo-IP-Country
This is the ISO 3166 alpha-2 country code we determined for the requesting IP address. This could be useful if your integration is client-side only. e.g. FR
Octo-IP-Currency
This is the ISO 4217 currency code we determined for the requesting IP's country. This could be useful if your integration is client-side only. e.g. EUR
Octo-Env
This will return test if the request is in test, or live if it wasn't.
Content-Language
This is the language of the content being returned. See the Localization section for info how to set it.

Products

Localization

Last modified 1yr ago

Header	Description
`Accept-Language`	This conforms to the regular HTTP specification for language but if the supplier has translated their content it will return the content in the specified language if possible. Also all error messages will be translated. eg. `Accept-Language: fr` the server will then respond with `Language: fr` depending on if that language was available.
`Octo-Env`	This header will mark any booking you perform with live credentials as a test sale. This will mean it will not consume any availability, the barcodes will not work, and you will not be invoiced for it. e.g. `Octo-Env: test` and to turn it off, change the value to `live`.
`Content-Type`	This must be `application/json` for all `POST` `PATCH` and `DELETE` requests.
`Referer`	This is only used with checkout connections but allows a sale to be associated to a reseller using their referer.

Header	Description
`Octo-Capabilities`	A list of the capabilities that were initialised with this request. e.g. `Octo-Capabilities: octo/pricing, octo/content`
`Octo-IP-Country`	This is the ISO 3166 alpha-2 country code we determined for the requesting IP address. This could be useful if your integration is client-side only. e.g. `FR`
`Octo-IP-Currency`	This is the ISO 4217 currency code we determined for the requesting IP's country. This could be useful if your integration is client-side only. e.g. `EUR`
`Octo-Env`	This will return `test` if the request is in test, or `live` if it wasn't.
`Content-Language`	This is the language of the content being returned. See the Localization section for info how to set it.