Contract
Support
Where to send a problem, and what we will and will not promise about answering it.
Reporting a problem
Email info@swisstouristy.com. Include the request_id from the error body — it identifies the exact request in our logs and turns a vague report into a specific one.
Security
For anything with a security dimension — a token doing more than its scope should, one caller reaching another caller's quote, a leak in a response body — write to the same address with SECURITY in the subject and please do not open a public report first.
There is no support SLA
We do not publish a response-time commitment for this surface, and you should not plan around one. Saying so plainly is more useful than a number nobody has agreed to underwrite. If your integration needs a contractual response time, that is a commercial conversation, not a documentation one.
Before you write
- Check the error reference — every code carries a
next_action, and most problems are one of the seventeen. - A
401on a token you believe is good is usually the audience: it is an identifier, not an address. See authentication. - If the document and this site disagree, the document is right — it is generated from the running routes.