Authentication

EurostatAPI accepts two authentication paths. The RapidAPI gateway path is the default — you subscribe on RapidAPI, they issue you a key, you send it as X-RapidAPI-Key, and their gateway forwards the request to our backend. The direct path is for enterprise contracts — we issue an Aethar-native key with the prefix eu_ and you send it as X-API-Key directly to https://eurostat.wageapi.com/api.

Both paths enforce the same rate limits per key. Pick the path that matches where you got your key.

X-RapidAPI-Key:  your_rapidapi_key_here
X-RapidAPI-Host: eurostat-eu-economic-data-api.p.rapidapi.com

Base URL: https://eurostat-eu-economic-data-api.p.rapidapi.com. Keys are tied to your RapidAPI account and plan — rotate them from the RapidAPI dashboard.

X-API-Key: eu_your_direct_key_here

Base URL: https://eurostat.wageapi.com/api. Keys start with the prefix eu_ followed by an opaque random string. Never send keys in query parameters, cookies, or request bodies — only in the X-API-Key header.

Direct keys can be scoped to a subset of endpoints (e.g. eurostat:read only). RapidAPI keys inherit their scope from the subscribed plan.

If you call an endpoint your key lacks scope for, you get 403 SCOPE_DENIED with a pointer to the upgrade page.

401 MISSING_API_KEY — no key header sent. Most common cause: you forgot the header on your curl.

401 INVALID_API_KEY — header present but value not recognised. Check for typos and make sure you copied the full key (no trailing whitespace).

403 SCOPE_DENIED — key is valid but lacks the scope the endpoint needs. Upgrade your plan on RapidAPI or ask us for a broader direct key.

RapidAPI: regenerate from your RapidAPI dashboard. The new key is active immediately.

Direct: open a ticket and we'll issue a new key + revoke the old one. Revoked keys stop working immediately — no grace period.