Resources
Support
How to get help, and what to include so the first reply is a useful one.
Reporting a problem
For anything involving a specific request, include these four things. With them a failure can usually be traced in one lookup; without them the first reply is a request for them.
- The request id, from the X-Request-Id header or the request_id field in the error.
- The method and path you called, and the API key prefix — the part before the dot, which is safe to share.
- When it happened, with a timezone.
- The request body, with any personal data removed. Never send the secret half of an API key or a webhook signing secret.
The request id is returned on every response, not only failures. Logging it for successful calls too is what makes it possible to investigate a message that was accepted but behaved unexpectedly.
Done in the console, not the API
Creating and revoking API keys, registering sender IDs, editing or deleting a webhook endpoint, cancelling a batch in flight, and topping up the wallet are all console operations. If your integration needs one of them automated, get in touch and tell us the use case.