Code Connect: API Marketplace

The following headers are used in requests sent to Code Connect APIs.

Header name	Required?	Description	Example
`uuid`	Yes	Identifies a specific API interaction for tracing purposes. Format: 36 character string, as defined by RFC 4122	`uuid: 9725593d-436c-4404-8a51-5afd51ba977a`
`Content-Language`	No	Describes locale information if a resource (that can be localized) is returned with a different locale from the default. Format: 2 character string, as defined by RFC2616#section-14.12	`Content-Language: en`
`Content-Type`	No*	Identifies the MIME type of the message body. Format: As defined by MDN Content Type	`Content-Type: text/html; charset=utf-8`
`Authorization`	Yes	The authorization method for a request to a Code Connect API. APIs may require additional authorization headers/methods beyond Authorization. Check your API solution for more information. Format: As defined by MDN Authorization	`Authorization: Bearer [bearer token value]`
`Access-Control-Request-Headers`	No*	Identifies the comma-separated list of HTTP request headers that will be used during an API request. *This header is used by browser-based API clients. Format: As defined by MDN Access-Control-Request-Headers	`Access-Control-Request-Headers: content-type,x-pingother`
`Access-Control-Request-Method`	No*	Identifies the comma-separated list of HTTP request methods that will be used during an API request. *This header is used by browser-based API clients. Format: As defined by MDN Access-Control-Request Headers	`Access-Control-Request-Method: POST`
`source-id`	No*	Identifies the application invoking the API. This value is provided by FIS. *This header is used when an implementation requires a specific source ID.	`source-id: randomString`
`Accept`	No	Use this header to specify to the server implementation the MIME types it can process. Format: As defined by rfc2616#section-14.1	`Accept: text/html`
`Accept-Charset`	No	Use this header to specify to the server what character sets are acceptable for the response. Format: As defined by rfc2616#section-14.2	`Accept-Charset: iso-8859-5`
`Accept-Encoding`	No	Similar to `Accept`. Use to restrict the content-encodings that are acceptable in the response. Format: As defined by rfc2616#section-14.3	`Accept-Encoding: compress, gzip`
`Accept-Language`	No	Used to restrict the natural languages that are preferred as a response. Format: As defined by rfc2616#section-14.4	`Accept-Language: en`

* = This header is conditionally required. Refer to the header description for the requirement conditions.