HTTP Headers
Breaking Down HTTP Headers
The following table lists the custom API request and response headers that are used for Verto APIs. Besides these custom headers, certain standard HTTPS headers are used as well. You can read more about the Standard HTTPS header field definitions here.
API Request Headers
HTTP Request Header Field | Description | Sample Value |
|---|---|---|
Accept (Optional) | Indicates a data type expected in a response sent from the server, so it's used as a response header |
|
Accept-Encoding | List of acceptable encodings. This restricts the content-codings that are acceptable in the response. Currently, Verto APIs support gzip, deflate, br, and zstd. See HTTP compression. |
|
Accept-Language | Language in which you want to receive the response. |
|
Authorization | Allows internet users to access applications, services, websites, and application programming interfaces (APIs) without having to enter their login credentials each time they visit. |
|
Content-Type | This is used to identify the type of request. Currently, Verto APIs support only |
|
Vfx-Correlation-Id | Unique ID that is used to track calls made in the same session |
|
API Response Headers
| HTTP Response Header Field | Description | Sample Value |
|---|---|---|
| Content-Type | This is used to identify the type of request. Currently, Verto APIs support only application/json. | application/json; charset=utf-8 |
| Vfx-Api-Call-Id | A unique verto identifier that's automatically generated for each api call (also known as API request). | df96e634-0d34-4882-14c4-dee1f0bf25e2 |
| Vfx-Api-Stack-Id | The identifier for the specific API stack being utilized. | 34d13709-1964-364c-f9f4-2f15d823203e |
| Vfx-Correlation-Id | A unique verto identifier that's automatically generated for each request that enters a system. It is used to track the request as it makes its way through the system. | 0e924cdf-c0aa-4673-bb36-2262325ed30b |
Updated over 1 year ago