Headers
You must supply a set of HTTP headers when making a request. These headers can include both standard HTTP headers as well as some custom OCTO API or Ventrata headers.
Below are the required standard request headers, custom headers we recommend using, as well as some useful headers you can expect in Ventrata responses.
Request Headers
Header | Required | Description |
---|---|---|
| Required | Your Authentication |
| Required | This must be |
| Required | A list of the Capabilities to be included in the response e.g. |
| Recommended | 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 |
| Optional | 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. |
Response Headers
Header | Description |
---|---|
|
|
| A list of the Capabilities you initialized with your request. e.g. |
| This will return |
| This is the language of the content being returned. See the Localization section for info on how to set it. |
| A list of languages the supplier has translated the content into. See Localization |
Last updated