Accredible · Rate Limits

Accredible Rate Limits

Accredible does not publish fixed numeric rate limits for its REST API in the public API reference. The practical governor on issuance volume is the plan's annual unique-recipient allowance rather than a per-minute request cap. Clients should treat the API as rate-limited in principle - implement exponential backoff, honor any Retry-After header, and prefer the bulk-create endpoint over many single-credential calls for large batches. The API authenticates each request with an API key in the Authorization header (`Token token=YOUR_API_KEY`); an invalid key returns 401.

Accredible Rate Limits is the machine-readable rate-limit profile for Accredible on the APIs.io network, in the API Commons Rate Limits shape.

It captures 3 rate-limit definitions, measuring requests, recipients, and credentials.

An exhausted limit returns HTTP 429.

This profile was written by API Evangelist and has not been verified against a page the provider published; treat every limit as unconfirmed until a dated transcription replaces it.

The profile also includes 3 backoff/retry policies defined and response codes documented for throttled and unauthorized.

Tagged areas include Digital Credentials, Certificates, Badges, Rate Limiting, and Quotas.

3 Limits Exhausted: HTTP 429
Method: generated, dated 2026-07-05.
Written by API Evangelist on 2026-07-05 and not verified against a page the provider published. Treat every limit as unconfirmed until a dated transcription replaces it.
View Source
Digital CredentialsCertificatesBadgesRate LimitingQuotas

Limits

API Requests account
requests
not published
No fixed numeric request-rate limit is documented for the Accredible API.
Recipient Allowance account
recipients
per plan (per year)
Issuance is governed by the plan's annual unique-recipient allowance rather than a request-rate cap. Unlimited credentials per unique recipient.
Bulk Create Batch request
credentials
batch via /credentials/bulk_create
Prefer bulk_create over many single POST /credentials calls for large issuances.

Policies

Backoff Strategy
Clients should implement exponential backoff with jitter and honor any Retry-After header on 429 responses.
Bulk Preferred
Use the bulk_create endpoint for large batches to reduce request volume and avoid throttling.
Sandbox Testing
Run high-volume or load-sensitive tests against the sandbox environment (sandbox.api.accredible.com) rather than production.

Sources

Work with this as data

Every rate limit here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for rate limits

4 MCP tools reach this
  • find_rate_limitsBrowse and filter every rate limit in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This rate limit 
curl "https://apis.io/api/v1/rate-limits/accredible-rate-limits"
All rate limits 
curl "https://apis.io/api/v1/rate-limits?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.