After API Umbrella verifies an incoming request (a valid API key, below rate limits, etc), it will then proxy the incoming request to your API backend. The request your API backend receives will have additional HTTP headers added to the request. These headers can optionally be used to identify details about the requesting user.
A unique identifier for the requesting user (UUID format). This should be used if your API backend needs to uniquely identify the user making the request.
If the user accessing the API has roles assigned to them, these will be present in the
X-Api-Roles header as a comma-separated list of roles:
X-Api-Roles: (comma separated list)
Used for identifying the original IP address of the client. See X-Forwarded-For for usage and details.
X-Forwarded-For: (comma separated list)
X-Forwarded-For: 203.0.113.54, 198.51.100.18
The original protocol of the client’s request (either
https). This can be used to determine how the client originally connected to the API regardless of what protocol is being used for API backend communication.
X-Forwarded-Proto: (http or https)
The original port of the client’s request (for example,
443). This can be used to determine how the client originally connected to the API regardless of what port is being used for API backend communication.
A unique string identifier for each individual request. This can be used in log data to trace a specific request through multiple servers or proxy layers.
X-Api-Umbrella-Request-Id: (unique string identifier)
Currently the API passed in by the user is passed along to API backends in the
X-Api-Key header. However, this header is deprecated and will be removed in the future. Instead, the
X-Api-User-Id should be used if you need to uniquely identify the requesting user.
X-Api-Key: (api key)