API: errors, limits and retries
Handle errors and uncertain outcomes without duplicate purchases.
Last updated:
How it works, step by step
- Check both HTTP status and JSON: application errors may use HTTP 200 with error. Invalid keys return 401; add can return 403 with EMAIL_NOT_VERIFIED.
- For 429, respect Retry-After. Per key, per 60 seconds: services 30, balance 60, add 120, status 300 and refill 60.
- Refresh the catalog for inactive services, correct links and quantities, and check credit for insufficient funds. An error response is not a successful order.
- Timeouts or 503 can leave an order under review. Keep idempotency_key, check orders and contact support before retrying uncertain purchases. Store secrets in environment variables, redact logs and revoke exposed keys.
Important
Do not switch API key or idempotency_key to bypass an error: this breaks the reference used to avoid duplicate orders.
API examples
status
curl --request POST https://nexwa.store/api/v2 \
--header "Authorization: Bearer ${NEXWA_API_KEY}" \
--data-urlencode "action=status" \
--data-urlencode "order=${NEXWA_ORDER_ID}"Open the feature
Was this guide helpful?
Local feedback is not sent to support. Use the contacts below to receive a reply.
Still need a hand?
Open account support for a specific request. If you cannot sign in, email us.