Headers accompany the body of a request, containing information about the request and how to process it. All Tigrillo APISMS API requests use the same headers.
If you are using Postman, the following headers are automatically generated.
|Object name||Default value (Postman)||Description||Required?|
Sends cookies that are associated with this endpoint.
We recommend using this header. Prevents the server returning a stale response when you make repeated requests.
|Postman-Token||<calculated when request is sent>||
If you are using Postman, we recommend this header, which appends a random UUID to every outgoing request. This aids debugging, by ensuring separate requests are distinct in the receiving server.
Helps the server identify the media type of the current request body.
|Content-Length||<calculated when request is sent>||
For parsing purposes. Indicates the size of the current request body to the server.
|Host||<calculated when request is sent>||
Helps the server identify the domain name where the request is sent.
If you are using Postman, we recommend using this header. Helps the server identify Postman as the HTTP requesting application or client.
If you are using Postman, we recommend using this header. The "Accept: */*" header tells the server that Postman can understand and process all forms of response content types.
|Accept-Encoding||gzip, deflate, br||
If you are using Postman, we recommend using this header. For parsing purposes. Indicates to the server that the Postman HTTP client supports a defined list of content-encoding or compression algorithms as response.
We recommend using this header. Indicates to the server to keep the underlying network connection open after receiving the current response. This enables you to reuse the same connection for faster response times in subsequent requests to the same server.