This must be
application/json for all
A list of the Capabilities to be included in the response e.g.
Octo-Capabilities: octo/pricing, octo/content, etc. Include the header, but leave it empty if no capabilities are needed. When this header is not included, Ventrata's response will result in a 400 error.
This header can mark any booking you perform with live credentials as a test sale in Ventrata. This will mean it will not consume any availability, the barcodes will not work, and you will not be invoiced for it. Use
Octo-Env: test for test bookings and
Octo-Env: live to turn it off and sell live. See Live Testing.
This conforms to the regular HTTP specification for the 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. See Localization.