X-Request-ID response header) for faster diagnosis.
Authentication errors
401 Unauthorized
A401 response means your API key is missing, malformed, or invalid.
Check:
- The
Authorizationheader is present and formatted asBearer YOUR_API_KEY - Your API key is correct — copy it fresh from Settings → API Keys if unsure
- The key hasn’t been revoked (check the dashboard — revoked keys show a red status)
- You’re using the right key for the right environment (
sk_test_for sandbox,sk_live_for production)
403 Forbidden
A403 means your key exists but lacks permission for the operation.
Check:
- The key’s scope —
read-scoped keys cannot create or modify resources - Any IP allowlist configured on the key — requests from unlisted IPs are rejected
write) from Settings → API Keys.
Rate limit errors
429 Too Many Requests
You’ve exceeded your rate limit for the current window. Resolution:- Check the
Retry-Afterheader in the response — it tells you exactly how long to wait - Implement exponential backoff in your client
- Reduce request frequency or batch operations where possible
- Upgrade your plan for higher limits
Webhook delivery failures
Endpoint not receiving events
Check:- Your endpoint URL is publicly accessible (not
localhostor a private IP) - The endpoint accepts
POSTrequests - The endpoint responds with
200 OKwithin 10 seconds - The correct event types are selected in Webhooks → Edit
Signature verification failing
If your HMAC verification is failing:- Ensure you’re hashing the raw request body (not parsed JSON)
- Check that you’re using the correct webhook secret from your dashboard
- Confirm you’re comparing the full signature string, not just a prefix
Re-delivering failed events
If a webhook delivery failed and you want to retry it:- Go to Webhooks → Delivery Logs in your dashboard
- Find the failed delivery
- Click Re-deliver to trigger a new attempt
Connection & timeout issues
Request timeouts
If requests are timing out before completing:- Check status.erynoa.group for any ongoing incidents
- Increase your HTTP client’s timeout setting (recommend at least 30 seconds)
- For long-running operations, use the asynchronous API pattern — submit a job and poll for completion
Slow responses
Occasional slowdowns can occur during high traffic. Steps to diagnose:- Check the
X-Request-IDheader in the response and note it for support - Check the ErynoaGroup status page for performance notices
- If persistent, contact support with the affected request IDs and timestamps
Getting help
If you can’t resolve an issue with this guide:- Email support: Include your request ID (
X-Request-ID), the full error response, and steps to reproduce - Dashboard logs: Check API Logs and Webhook Logs in your dashboard for detailed event history
- Status page: Check status.erynoa.group for real-time platform status