Support
One form, read by the people who build the thing. If you would rather write an email, [email protected] reaches the same place — the form only exists because it can collect the three things an answer usually needs before you have to go and look them up.
What happens after you send this
- It is filed with a reference of its own and read by a person. There is no auto-reply, no ticket portal to sign into, and no status page for your own request.
- There is no response-time commitment, and we would rather say so than publish a number nobody measures. Spaw is small. The honest version is that a request naming a request id and an endpoint is usually answered in one reply, and one that describes a symptom is a conversation.
- The Scale and Volume plans include priority support. In practice that means exactly one thing: your request is marked priority and sits at the top of the queue. It is not a faster promise, because there is no promise to make faster.
- If the API is down for everyone, the status page knows before support does. It is worth a look before writing.
- What you type is stored so it can be read and answered, and deleted 180 days after it arrives. Do not paste an API key, a card number or a password — nobody here will ever ask for one.
Things that are not support questions
- An answer you disagree with also has a report control under it in the dashboard, which feeds your own later lookups. Use both: the control moves the data, this form reaches a person.
- Every typed error explains itself at the error reference, and every verdict reason at the reason reference.