Support
Where to get help with Synq, how fast it answers, how you hear about an incident, and what to send.
Start with the error
Every error Synq answers with has a code, and every code has a page under Errors: what happened, whose side it's on, and what to do. Troubleshooting covers the usual sign-in and API problems.
Is Synq down?
Every incident is posted on Synq's status page as it happens, with updates until it's resolved. If sign-in stops working for your brand, your org's owners also get an email, from Synq, saying what's affected and linking the incident on the status page.
The status page checks Synq's sign-in, the API, the dashboard, the website and the docs from outside, every minute. It runs apart from the rest of Synq, so it still answers when Synq doesn't.
It covers production alone. The sandbox, Synq's preview stage, has no status
page: it's where your keys start sk_test_, its addresses carry preview- and its emails' subjects
[Preview]. When something there fails that the error's page doesn't explain, write to
support@synq.build, say it's the sandbox, and send what's listed
under What to send.
Write to us
- Anything about Synq: support@synq.build. It aims to answer within one business day (Mon–Fri, US Eastern), on every plan. The dashboard's error pages name the same address.
- Aerosol, the company that makes Synq: hello@aerosol.build, or call +1 (813) 670-2737.
- A security vulnerability: security@synq.build, privately, before telling anyone else.
What to send
- The
request_idthe error gave you, if it gave one. The management and account APIs put it in their problem documents and theRequest-Idheader (see API conventions). - The error's
code, and when it happened, with your time zone. - Your org's ID (
org_…), and the brand's or app's ID if it's about one (brd_…,app_…). They're in the dashboard's address bar. - What you did, what you expected, and what happened instead.
Never send a client secret, an API key, a webhook signing secret, or anyone's tokens. Synq never asks for them.