The required headers passed in a request are the following:
Format: ISO 639-1 language code
Explanation: This is the language the user is speaking and typing
Format:ISO 3166-1 alpha-2 region code
Explanation: This is the region from which a user’s content is locked to. This is used for example for streaming service selection and restriction, as well as news sources and many other domains
Format: Bearer Token
Example: Bearer ….
Explanation: This ties a request to our backend on behalf of that user. It is required that this be a JWT for the same UUID if you want to enable personalization or multi-turn support.
Explanation: API secret key that identifies the service sending these requests.
Explanation: This is the voice that is used for responses, i.e. the language a user wants to hear. If you are synthesizing voice on the frontend this represents the language to be used (sometimes called TTS field)
The optional headers passed in a request are the following:
Explanation: This is required if you want to be able to perform restaurant searches. It does not need to be exact and can also come from a GeoIP. If you have an exact location we suggest rounding it. We do not store the User-Location outside of the request log.
Format: ISO-8601 with timezone offset
Explanation: This is used to improve understanding, search, and personalization. It should match the device time used.
Format: int enum for spellcheck mode
0 = off
1 = on
Explanation: Defaults to on, set to 0 for a faster response if you have already done spelling correction and language modeling.