Support
When the API doesn't do what these guides say, tell Blazot, with enough detail for Blazot to find your request.
Before you write
- Check the error. Errors says what each status and
codemeans and what to do about it. Most401s and429s have a fix on your side. - Check that the API is up.
GET https://api.blazot.com/v2/metaneeds no token and isn't rate-limited: a200with"status": "ok"means the API is running.
How to reach Blazot
- Logged in: open your support messages (on Blazot, the menu in the upper right, then Support), and choose New Message. If you're asked to log in, Blazot then opens its home page: open Support from the menu. Write as the account that owns the key. For a Site's key, write as a user who manages the Site, and name the Site.
- Can't log in: use the contact form. It asks you to pass a quick check that you're a person, and Blazot replies to the email address you give.
What to include
- The
correlationIdfrom the error body. It identifies your request, and for a500it points to the exact entry in Blazot's logs. - The time of the call, with its time zone.
- The method and path, such as
GET /v2/users/exampleuser/transmissions, and the parameters you sent. - The status and the error body: its
codeanddetail. - Which key you used: your user account's or a Site's, and the username or Site name.
- What you expected to happen instead.
Important
Never put your API key, its secret or an access token in a support message. Blazot never asks for them. If one may have been seen by someone else, regenerate your keys.
More reads and new endpoints
A bigger read budget comes with a higher subscription level: Rate limits has the numbers. Ideas for new endpoints or fields are welcome too: send them the same way.