Status and help

Is it you or us?Copy Anchor Link

1. Read the error. Every error has a code and a message; Errors says what to do about each. A 4xx is almost always about the request; a 5xx is ours.
2. Check the key. GET /v2/me answers for any valid key and shows its scopes, environment, pin, allowlist and remaining rate limit.
3. Look at the request log. Developers → Logs shows every /v2 request for 14 days, with its status and request id.
4. For webhooks, open the endpoint in Developers → Webhooks: every attempt, its status or failure reason, and your server's response.

Gauge does not publish a public status page yet.

Contact supportCopy Anchor Link

Email support@gauge.chat, or use the help menu in the console. To get an answer quickly, include:

• the request id (X-Request-Id, or error.requestId) of a failing request;
• the time it happened, with your time zone;
• the endpoint and method, and the error.code you got;
• for a webhook, the endpoint URL and the event id.

Never send an API key or a signing secret, not even a test one. The key's prefix (shown in the console, like pulse_k_live_x9Qa) is enough to identify it.

Security issuesCopy Anchor Link

If you believe you have found a security vulnerability in Gauge, email support@gauge.chat with "Security" in the subject, and do not test it against other customers' data.