RapidAPI Proxy

RapidAPI access is authenticated by RapidAPI before requests reach Company Data Guys. Company Data Guys then accepts RapidAPI-originated requests only when the RapidAPI request transformation adds the configured proxy secret.

Supported proxy-secret headers:

x-rapidapi-proxy-secret: <configured secret>
railway-key: <configured secret>

When a valid proxy secret is present, the endpoint does not require a Company Data Guys customer API key. RapidAPI requests are logged separately with the hashed RapidAPI key, host, user, subscription metadata, status code, requested URL count, returned count, billed credits, cache hits, live fetches, and request duration.

RapidAPI success responses include billing headers:

X-RapidAPI-Billing: Companies=3
X-CompanyData-Billing: 3

The /health endpoint uses the same proxy-secret check and is intended for RapidAPI integration checks, not public site monitoring.