# Global Headers

## Content-Type header

The API supports `application/json` only.

Both payload and response body are supposed to be a valid JSON so when making a request send a `Content-Type: application/json` header.

If payload is not a valid JSON, then `400 Bad Request` HTTP code and empty response body are returned.

## X-User-Agent header

> Example header: `X-User-Agent: Infinity Mall Android App `

`X-User-Agent` is **required** to distinguish specific client for information and debugging purposes so we better know who uses the service.

It should be arbitrarily chosen to represent client specifics (e.g. 'Infinity Mall Android App v1.2' or 'Infinity Mall Backend Service')

## X-Product-Name

> Example header: `X-Product-Name: android-app`

Each system that is communicating with us should uniquely identify itself so it is possible to distinguish optin/update channels.
That will allow further targeting members by communication channel.

For that we use product name. It should be passed as **required** header `X-Product-Name` that is intended to provide the necessary granularity.

If you miss your product name, please <a href="mailto:support@placewise.com">let us know</a>.

## X-Loyalty-Club-Slug header

See: [LoyaltyClub Context](doc-342138)

## X-Customer header

See: [Customer Context](doc-342139)

## X-Client-Authorization header

See: [Client Authorization](doc-342128)

## X-Locale header

See: [Localization](doc-341959)

## Authorization header

See: [Member Authorization](doc-342129) or [User Authorization](doc-342130)