Accredible is a digital credentialing platform for issuing, managing, and verifying digital certificates and Open Badges. The REST API lets issuers create and update credentials (certificates and badges) for recipients, organize them into Groups (courses/achievements), apply reusable visual Designs, attach Evidence Items and References, generate PDFs and blockchain-verifiable records, pull engagement analytics, manage Departments and Team Members, and generate recipient SSO links. Credentials are issued against a Group and rendered with a Design; the platform hosts a public verification page and share links for each credential.
Accredible publishes 14 API contracts indexed on the APIs.io network, including Analytics API, Credentials API, Departments API, and 11 more. Tagged areas include Digital Credentials, Certificates, Badges, Open Badges, and Credentialing.
Accredible’s developer surface includes engineering blog, authentication, documentation, and 9 more developer resources.
Regulatory Posture applies to this provider. Its tags matched the
Horizontal (data, software, accessibility, platform) regime, so
Regulatory Posture carries 15 points of the composite.
If this regime is wrong for your business, say so on your
provider repo — the
applicability map is public and we will correct it.
Create-or-Update Ergonomics applies to this provider. This API accepts writes, so it
carries 10 points of the composite. It is scored from the published contracts
themselves: whether a caller can create-or-update in one call, whether the write accepts a key the caller already
holds, and whether the response says which branch ran. Without that, every write needs a search-and-branch in
front of it, and the first time that check is skipped a duplicate record is created.
Scored against the observed mean rather than raw — a provider at the catalog average is unchanged by this facet,
not penalised by it.
The six quality facets above are damped to 75 points between them,
because the conditional facet above carries the other
25. That is why each facet's contribution is shown against a damped
maximum: raising a quality facet moves the composite by 75% of its nominal
weight, not 100%. The full arithmetic is at apis.io/rating/.
Show this score on your site.
It updates itself when the score changes. Paste this where you link to your API docs:
<a href="https://apis.io/providers/accredible/"><img src="https://apis.io/badge/accredible/card.svg" alt="Accredible on APIs.io — Kin Score by API Evangelist"></a>
Other styles, a README pill and a shields.io endpoint are on the badge page.
Improve this rating by publishing the missing artifacts — every area above can be raised, and the full rubric is at apis.io/rating/. Every facet and dimension name above is a link: it opens that measurement's own page — what it means, the exact checks that feed it, how the whole catalog distributes on it, and the providers at the top of it. This rating is computed from github.com/api-evangelist/accredible: open an issue to ask a question, or submit a pull request to add artifacts.
Submit an artifact on GitHub — free →Manage your own listing — the Influence plan, $499/mo →
Markets this provider is in provisional
The Kin Score Market layer reads a provider inside its market:
its position, and how deep its integrations go. Depth is only comparable within a position. Provisional and unweighted:
not part of the Kin Score or agent readiness.
Registered MCP server and declares compatibility are report only — not weighted.
Undeclared means we found nothing we can read, so there is no number: we never infer integrations.
Attributes provide a way to add information to certificates/emails. A full guide on Attributes can be found here: https://help.accredible.com/a-quick-guide-to-attributes
A Collection is a curated set of groups. To create one, you'll need to provide a collection name, a description, and indicate whether it should be public or private. Once create...
A Skills Framework is a structured taxonomy of skills. Accredible maintains external frameworks such as O*NET, ESCO and NACE, and your organization can upload its own custom fra...
aid: accredible
url: https://raw.githubusercontent.com/api-evangelist/accredible/refs/heads/main/apis.yml
name: Accredible
kind: company
description: Accredible is a digital credentialing platform for issuing, managing, and verifying digital certificates and
Open Badges. The REST API lets issuers create and update credentials (certificates and badges) for recipients, organize
them into Groups (courses/achievements), apply reusable visual Designs, attach Evidence Items and References, generate PDFs
and blockchain-verifiable records, pull engagement analytics, manage Departments and Team Members, and generate recipient
SSO links. Credentials are issued against a Group and rendered with a Design; the platform hosts a public verification page
and share links for each credential.
deliveryModel:
model: saas
open_source: false
commercial: true
callable_host: true
label: Hosted service · you call their endpoint
confidence: high
source:
- openapi
- pricing
generated: '2026-08-28'
method: derived
accessModel:
pricing: paid
onboarding: unknown
trial: false
try_now: false
public: false
label: Paid
confidence: medium
source:
- plans
- authentication
- security
generated: '2026-09-03'
method: derived
image: https://kinlane-images.s3.amazonaws.com/shared/apis-json/icons/accredible.png
x-docs-platform: redocly
x-docs-platform-confidence: medium
x-docs-platform-checked: 2026-09-17
x-docs-hosting: cloudflare-pages
tags:
- Digital Credentials
- Certificates
- Badges
- Open Badges
- Credentialing
- Verification
- Digital Badges
created: '2026-07-05'
modified: '2026-10-06'
specificationVersion: '0.23'
apis:
- aid: accredible:accredible-analytics-api
name: Accredible Analytics API
description: Issuer-level and per-credential engagement analytics.
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- Analytics
properties:
- type: OpenAPI
url: openapi/accredible-analytics-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
- aid: accredible:accredible-credentials-api
name: Accredible Credentials API
description: Issue, retrieve, update, delete, search, and verify digital credentials.
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- Credentials
properties:
- type: OpenAPI
url: openapi/accredible-credentials-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
- aid: accredible:accredible-departments-api
name: Accredible Departments API
description: Independent sub-organizations within an issuer account.
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- Departments
properties:
- type: OpenAPI
url: openapi/accredible-departments-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
- aid: accredible:accredible-designs-api
name: Accredible Designs API
description: Reusable visual specifications for rendering badges and certificates.
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- Design
tags_raw:
- Designs
properties:
- type: OpenAPI
url: openapi/accredible-designs-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
- aid: accredible:accredible-evidence-items-api
name: Accredible Evidence Items API
description: Supplemental work samples attached to a credential.
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- Evidence Items
properties:
- type: OpenAPI
url: openapi/accredible-evidence-items-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
- aid: accredible:accredible-groups-api
name: Accredible Groups API
description: Course or achievement containers that credentials are issued against.
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- Group
tags_raw:
- Groups
properties:
- type: OpenAPI
url: openapi/accredible-groups-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
- aid: accredible:accredible-references-api
name: Accredible References API
description: Peer, teacher, or manager endorsements attached to a credential.
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- References
properties:
- type: OpenAPI
url: openapi/accredible-references-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
- aid: accredible:accredible-sso-api
name: Accredible SSO API
description: Recipient single sign-on link generation.
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- SSO
properties:
- type: OpenAPI
url: openapi/accredible-sso-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
- aid: accredible:accredible-team-members-api
name: Accredible Team Members API
description: Administrators and roles within the issuer account.
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- Team Members
properties:
- type: OpenAPI
url: openapi/accredible-team-members-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
- aid: accredible:accredible-attributes-api
name: Accredible Attributes API
description: 'Attributes provide a way to add information to certificates/emails. A full guide on Attributes can be found
here: https://help.accredible.com/a-quick-guide-to-attributes'
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- Attributes
properties:
- type: OpenAPI
url: openapi/accredible-attributes-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
- aid: accredible:accredible-collections-api
name: Accredible Collections API
description: 'A Collection is a curated set of groups.
To create one, you''ll need to provide a collection name, a description, and indicate whether it should be public or private.
Once created, you can assign groups to the collection using the Groups APIs.'
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- Collection
tags_raw:
- Collections
properties:
- type: OpenAPI
url: openapi/accredible-collections-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
- aid: accredible:accredible-data-exports-api
name: Accredible Data Exports API
description: The following endpoints require the `data_exports` feature to be switched on, which is based on your pricing
plan.
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- Data Export
tags_raw:
- Data Exports
properties:
- type: OpenAPI
url: openapi/accredible-data-exports-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
- aid: accredible:accredible-issuers-api
name: Accredible Issuers API
description: The Issuers API from Accredible — 1 operation(s) for issuers.
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- Issuers
properties:
- type: OpenAPI
url: openapi/accredible-issuers-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
- aid: accredible:accredible-skills-frameworks-api
name: Accredible Skills Frameworks API
description: 'A Skills Framework is a structured taxonomy of skills. Accredible maintains external frameworks such as O*NET,
ESCO and NACE, and your organization can upload its own custom frameworks. Tagging a Group against a framework replaces
the free-text `learning_outcomes` list with skills that carry a stable identifier and a known position in a recognized
taxonomy.
These endpoints are **read-only**. Uploading frameworks, editing their skills, publishing and retiring versions are all
managed in the [Accredible Dashboard](https://dashboard.accredible.com/) — the API lets you discover the frameworks available
to you, search their skills, and select those skills on a Group.
## Frameworks are versioned
You always tag against a **version**, never a framework. Each framework in the list response carries a `versions` array;
take the `id` of the version you want and send it as `skill_framework_version_id` when you create or update a Group. Only
published versions (`active` and `retired`) are ever returned.
The version''s status decides what a write does. Tagging against the `active` version attaches your skills. Tagging against
a `retired` version never fails the request — the Group is still created or updated, but the skills are ignored and the
response is a `207` with a `version_retired` error.
## Skills know where they live
A skill sits at a position in its framework''s hierarchy, and in some taxonomies it legitimately sits in more than one.
The skills search response returns one row per skill with a `breadcrumbs` array — one trail per placement, each trail
listing the skill''s ancestors from the root down to its immediate parent.
When you attach a skill to a Group you send both the skill `id` and the `breadcrumb_ids` of the trail you mean, so the
placement is unambiguous. The ids in a `breadcrumbs` trail are exactly what `breadcrumb_ids` expects — you can copy them
straight from a search result into a Group request. Because the pair `(id, breadcrumb_ids)` identifies a placement, the
same skill id may appear more than once with different trails.
## Reading skills back off a credential
You do not need to call these endpoints to display a credential''s skills. [Credential](#tag/Credentials) responses carry
a `skills` array for the Group the credential was issued from, with each skill''s external `identifier` and its `breadcrumbs`
trail, so a consumer pulling credentials can render skills without a second request.
The framework those skills belong to is a property of the Group, not of the credential, so it is not repeated on every
credential. Follow the credential''s `group_id` to [View a Group](#operation/View%20a%20Group) and read `skill_framework`
— the Group response carries the same `skills` array alongside it.
The array is empty when the Group uses free-text `learning_outcomes`, when it has a framework selected but no skills that
can be tagged, and when the credential has no Group at all.
## Relationship to existing Group fields
Framework skills and free-text `learning_outcomes` can both be set on a Group; neither is rejected or cleared by the other.
Where a credential displays a single skills list, framework skills take precedence. `skill_category_id` is a separate,
unrelated classification and is unaffected.
## Skills that cannot be attached return a 207, not a failed write
When skills cannot be attached — because the version is retired, the framework is not available to the Department, a skill
id is not in the version, or a breadcrumb trail is invalid — the Group write does not fail. The Group is still created
or updated, every valid skill is attached, the rest are ignored, and each reason is itemized in the `errors` array of
a `207 Multi-Status` response. Attachment is per-skill, so one invalid skill does not stop the others from attaching.
Read `skill_framework` and `skills` off a `207` response to see exactly what was saved.
There is one exception. If your plan does not include access to skills frameworks and you send framework parameters for
a Group that is **already** framework-backed, [Update a Group](#operation/Update%20a%20Group) returns a hard `403` and
nothing in the request is saved, including changes to unrelated fields. The Group''s framework and skills stay saved and
readable, and moving it to free-text skills with `"framework_skills": null` is still allowed.
See [Skills Frameworks Error Handling](#section/Errors/Skills-Frameworks-Error-Handling) for the full list of codes.'
humanURL: https://docs.api.accredible.com/
baseURL: https://api.accredible.com/v1
tags:
- Skills Frameworks
properties:
- type: OpenAPI
url: openapi/accredible-skills-frameworks-api-openapi.yml
- type: Documentation
url: https://docs.api.accredible.com/
- type: APIReference
url: https://docs.api.accredible.com/
- type: PostmanCollection
url: collections/accredible.postman_collection.json
- type: OpenCollection
url: collections/accredible.opencollection.json
common:
- url: https://www.accredible.com/blog
type: Blog
- type: AgenticAccess
url: agentic-access/accredible-agentic-access.yml
- type: TrustCenter
url: security/accredible-trust-center.yml
- type: DomainSecurity
url: security/accredible-domain-security.yml
- type: Authentication
url: authentication/accredible-authentication.yml
- type: GitHubOrganization
url: https://github.com/accredible
- type: LinkedIn
url: https://www.linkedin.com/company/accredible
- type: Website
url: https://www.accredible.com
- type: Documentation
url: https://docs.api.accredible.com/
- type: Plans
url: plans/accredible-plans-pricing.yml
- type: RateLimits
url: rate-limits/accredible-rate-limits.yml
- type: FinOps
url: finops/accredible-finops.yml
maintainers:
- FN: Kin Lane
email: kin@apievangelist.com
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.
Kin Score
How this is scored →
It updates itself when the score changes. Paste this where you link to your API docs: