Go to production
Run through this list before your integration takes real traffic. Each item links to the page that covers it.
A production call checks for errors, logs the request id, and waits out a 429. Here is a Data API call that does all three:
- Keep the secret key on your servers. Store it in an environment variable, never in code, a browser, or a URL. See authentication.
- Give each app its own publishable key, with only the scopes it needs. A key that administers your account carries
managementalone and stays on your backend. See scopes. - Plan for rotation. Create the new key, deploy it, then revoke the old one under Organization → API keys. Tokens minted with a revoked secret key keep working until they expire, at most five minutes.
- Mint tokens on your server and renew them before
expires_at, as authentication shows. - Reuse a token across visitors of a public page until shortly before it expires, rather than minting one per page view.
- Mint member tokens only for the person signed in to your own product, never for an id the page sends.
- Turn on Require session token under Organization → Security to hold every request made with your publishable key to a token from your server.
List every site that uses your key or embeds your maps under Organization → Security, including each subdomain. Remove localhost entries you only needed in development. See allowed domains.
- Wait out a
429for the secondsRetry-Afternames. See rate limits. - Send an
Idempotency-Keywith every Map Studio API write, and the same key on every retry. See idempotency. - Check
errorson every Data API answer, even under200 OK. See errors.
- Log
X-Request-Idbeside every failure. Support finds your request by it. - Watch your usage under Organization → Usage in the Mountaya app.
- Follow the status page at mountaya.instatus.com.
- Contact support at support@mountaya.com, with the request id.