Support
Where to ask, and what to include so the answer comes back fast.
Contact#
Email [email protected].
Before you write, it's worth a minute with Troubleshooting — most errors have a specific, boring cause.
What to include#
The difference between a one-round answer and a five-round thread is usually detail:
- What you did — the endpoint or the app, and the exact request if there was one. Redact tokens.
- What happened — the full error body and status code, not a paraphrase.
- When — a timestamp with a timezone. Logs are searched by time.
- What you expected instead.
- Your account email, and the app id if it involves a specific app.
Warning
Never send an API key, a Connect token, a client secret, or a password. We will never ask for one. If you already pasted a key somewhere, revoke it.
Reporting an app#
If a published app misbehaves — misleading listing, broken link, abusive content, or a scope request that doesn't match what it does — report it from its gallery page or email us. Listings can be hidden or removed after approval.
Reporting a security issue#
See Security. Give us a chance to fix an issue before disclosing it, and don't test against other people's accounts.
Feature requests#
Tell us what you were trying to build and where the platform got in the way. A concrete blocked use case is more actionable than a feature name.