Configure upstream authentication
Store your API's key so NODRA can send it with every forwarded call, and rotate it safely.
- Tutorial
On this page
What you'll achieve
Forwarded calls carry your API's key in the right header, and you can replace it without downtime surprises.
Prerequisites
- A key your API accepts in a request header.
- An API registered in NODRA, or one you're about to register.
1. Find the header your API reads
NODRA supports these header names: X-API-Key, Authorization, Api-Key, ApiKey, X-Auth-Token, X-Access-Token, X-RapidAPI-Key and Ocp-Apim-Subscription-Key. Pick the one your API expects.
2. Enter the full value
Enter exactly what should follow the header name. For bearer tokens, choose Authorization and include the scheme:
Authorization: Bearer sk_live_…
X-API-Key: 4f1c…3. Test
Run a test call. A 401 or 403 from your API means the key or the header is wrong.
4. Rotate later
On the API's page, under Upstream key, choose Replace key. Run the test again from the banner that appears. Revoke the old key in your own system only once the new one passes.
Expected result
The test call passes, and the response preview shows your data with the key removed. The key is never shown again in the dashboard.
Common mistakes
| Mistake | Fix |
|---|---|
| Putting the key in the upstream URL as a query parameter | Upstream URLs can't contain a query. Keys can only be sent as a header. |
Leaving out Bearer | With Authorization, the value is sent exactly as entered. |
Expecting callers' own Authorization header to reach you | NODRA never forwards it; only your stored key is sent. |