Sign in to your NextGen dashboard
Don't have an account?
Request access
Enter your email to get a reset link
Find API reference guides, setup webhook endpoints, and troubleshoot code errors.
The NextGen API uses Bearer Tokens to authenticate requests. You can view and manage your API keys in the Developers Dashboard.
Your API requests must include an `Authorization` header formatted as: `Bearer sk_live_YOUR_SECRET_KEY`. Requests made over plain HTTP or without authentication will fail.
Webhooks allow NextGen to notify your application asynchronously when events occur, like a successful payment or a disputed charge.
To receive webhooks, navigate to Developers > Webhooks and click "Add Endpoint". Provide a valid HTTPS URL on your server. You must also verify webhook signatures using your endpoint secret to ensure the payload actually came from NextGen.
To ensure platform stability, NextGen enforces rate limiting on API requests. Standard accounts are limited to 100 read/write requests per second.
If you exceed this limit, the API will return a `429 Too Many Requests` status code. We highly recommend implementing exponential backoff logic in your code to automatically retry failed requests.