Request IDs and headers
Every answer from every Mountaya API carries an X-Request-Id. Log it beside every failure, and quote it when you contact support: it finds your request among all the others.
Browsers on other origins can read all of these through CORS.
Mountaya answers each request by the state it reads as the request arrives. Revoking a key or rotating a share link takes effect on the next request. Only public answers, such as a published itinerary or a public tile, may be stored by a shared cache, for at most a few minutes.
Each request runs under a time budget: 30 seconds, and 55 for an import. Past it, the API answers 504 Gateway Timeout. Let your HTTP client wait a little longer than the budget, so it never abandons an answer that was coming.
The TypeScript client applies all of this for you. It sends an Idempotency-Key with every write, waits out Retry-After, and follows cursors with paginate. Every error carries its requestId.