/status polls have their own budget, so tracking swaps never eats into quotes and executes.
Public and secret keys
Each self-serve key comes as a pair, shown once at signup.
Both count against the same rate limit and earn the same fee. RAVN stores only a hash of the secret
key, so it can’t show it again. Leaked it? Rotate it with
POST /v1/keys/secret:
the old one stops working within a minute.
Lock your public key to your sites. Set allowedOrigins with
PATCH /v1/keys. Browser requests from any other site are refused.
Requests without an Origin header (your servers) always work.
Key from before secret keys existed? It keeps full rights until 1 December 2026. Claim its
secret now with
POST /v1/keys/secret, from your server, sending the current key: from then on the
current key is your public key. Claim it first if the key is in browser code, since only one claim
is allowed. If the claim is refused, contact RAVN.Browsers and headers
CORS is enabled on every endpoint, so browser apps can call the API directly. Every response carriesx-request-id: quote it when you contact support. Rate-limited endpoints also send:

