You can change the behavior of the API engine by specifying
oneof the following HTTP headers as part of your requests:
AuthorizationHTTP header provides the authentication token as part of a request. Most REST calls must include an authentication token.
If you have specified an HTTP authentication provider as the authentication provider for your API, then this header is might not be relevant. The authentication provider handles authentication in a different way typically.
For more information about HTTP authentication providers, see Authenticate API Users using an HTTP Authentication Provider.
Authorization: CALiveAPICreator abcdef123456:1
:1suffix at the end of the authentication token is required.
Content-TypeHTTP header specifies the format of the payload (for example, JSON and XML). This HTTP header is applicable only for POST and PUT.
AcceptHTTP header is applicable to all requests. It indicates the format the caller can handle in the request.
The default response format is JSON. You can change this response format.
You can set the expected response format globally across your API. For more information about how to do this, see API Properties.
ForwardedHTTP header indicates that the API user is forwarding the request on behalf of another caller. Gateways often used this HTTP header.
The following HTTP header changes the base URLs in the response to the protocol, host, and port number that you specify. For more information about the RFC 7239 standard, see the ietf.org site.
X-Forwarder-Host/Proto/ForHTTP header is equivalent to the
ForwardedHTTP header. The
ForwardedHTTP header is the preferred header.