Understand Request Headers
- 1 Minute to read
- DarkLight
Understand Request Headers
- 1 Minute to read
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
This topic describes the API request header for authentication. It is assumed that you have already set-up all the prerequisites as required before using the API. You must pass certain parameters in the header of each request based on the approach used for authenticating the request.
The following table lists the header parameters and the description for the same using the APP ID and APP KEY that are passed in the API Request header for all the endpoints:
| Name | Required for Authentication | Description |
|---|---|---|
| x-app-id string (header) | Yes | Your Application ID issued from developer.nutritionix.com. A unique identifier to represent the end-user who is accessing the Nutritionix API. |
| x-app-key string (header) | Yes | Your Application Key issued from developer.nutritionix.com. A unique identifier to represent the end-user who is accessing the Nutritionix API. |
| x-remote-user-id | If in development mode, set this to 0. This is used for billing purposes to determine the number of active users your app has. |
Note:
When authenticating with the API, you must send the x-app-id and x-app-key params as headers, and not as query string parameters.
Was this article helpful?