Stuck? Talk to the people who built it.
[email protected]
For anything: a failing call, a confusing doc, a missing capability, an integration review. Goes to the engineering team, on every plan.
Write to usIn-app chat
Chat inside graph8
The fastest loop once you have an account: open the chat in the app and your org context rides along, so nobody asks you for IDs.
Open the appSelf-serve
Docs, FAQs, status
Auth, errors, rate limits, pagination, and a FAQ per surface. If something looks down, check what is available in the preview first.
Four things that turn one reply into the fix.
Every request is logged with an ID. Send it with your email and the first response is usually the answer, not a question.
Your org ID
Every key is bound to one org; it scopes the investigation.
The request ID
From the response headers or your request logs. One ID beats ten screenshots.
Endpoint + timestamp
What you called, when, and what you expected back.
The error body
Paste the JSON error envelope, not a screenshot of it.
Where to find request IDs: request logs ยท the error envelope