API and Webhooks plans and limits

Access to the REST API and to Webhooks depends on your organization’s active plan, not on whether your team already created an API Key or configured a webhook. If your plan doesn’t include one of these two capabilities, the platform will tell you the moment you try to use it.

What happens if your plan doesn’t include the API

If you try to authenticate against /login as an API user, or call any protected endpoint of the public API, and your organization doesn’t have the plan that enables API access, the response is:

HTTP 402 Payment Required

🔎 Note: the code is 402, not 401. A 402 means “your plan doesn’t include this,” not “your token is invalid” — if you see a 402, it’s not an authentication problem, it’s a plan issue.

This code applies both to the API User login and to any protected endpoint at https://public-api.acreditta.com. The exception is /credential/record/{credentialId}, which stays accessible without this check for compatibility with older record/PDF integrations.

What happens if your plan doesn’t include Webhooks

If your organization doesn’t have the plan that enables webhooks, any call to /api/v1/integrations/webhooks/* responds with:

HTTP 400 Bad Request

And in the admin panel, the Webhooks tab (inside Integrations → API) is replaced with a notice to upgrade your plan, instead of showing you the creation form.

How to check whether your plan includes these capabilities

The most direct way is to try creating an API Key or a webhook from the panel: if your plan doesn’t include them, the interface itself tells you, with an option to upgrade your plan. If you have questions about what your current plan includes, contact your account executive or tech@acreditta.com.

Next step

• Getting started with the API
• Webhook configuration