Support
How to get help with ZapAPI — community channels, email support, status page and reporting security issues.
We are here to help. Pick the channel that fits your issue.
Before you reach out
A surprising number of questions are answered in the docs:
- "How do I …?" — try the search bar (top of every page) or the Quickstart.
- "Why is my request failing?" — see Errors and
check the
codefield in the error response. - "Is ZapAPI down?" — check the status page first.
- "What changed?" — see the Changelog.
Channels
| Channel | Best for | Response time |
|---|---|---|
| GitHub Discussions | Design questions, integration patterns, feature requests | Best-effort, community-driven |
| GitHub Issues | Bug reports with a minimal reproduction | Triaged weekly |
Email — support@zapapi.com | Account, billing, and private integration questions | 1–2 business days |
Email — security@zapapi.com | Security vulnerabilities only | 24 hours |
Reporting a bug
A great bug report gets a fast fix. Please include:
- What you expected vs what happened.
- A minimal reproduction — the smallest
curlcommand or code snippet that shows the problem. - The request id from the
X-Request-Idresponse header (if any). - Environment — SDK version, runtime, and whether you are in test or live mode.
Redact any API keys, secrets, or customer data before pasting logs.
Reporting a security vulnerability
Do not open a public issue. Email security@zapapi.com with:
- A description of the vulnerability and its impact.
- Steps to reproduce (a proof-of-concept is ideal).
- Any affected endpoints or resources.
We follow coordinated disclosure: we will acknowledge your report within 24 hours, keep you updated on the fix, and credit you in the release notes (if you want) once the fix is deployed.
Status page
Real-time and historical uptime for the API, dashboard, and hosted checkout lives at status.zapapi.com. Subscribe to incident updates by email or RSS.
Enterprise support
For SLAs, dedicated support channels, and architectural review, contact
enterprise@zapapi.com.