Credly
Credly is a digital credential and open badge platform, owned by Pearson (acquired 2022), used by more than 2,000 organizations to issue, manage, and verify verifiable digital badges and certifications. The Credly Web Service API (base https://api.credly.com/v1, with a sandbox at https://sandbox-api.credly.com/v1) lets issuing organizations create and manage badge templates, issue and revoke badges to recipients, read organization and employee data, pull an events feed, and expose recipient credentials via Open Badges Infrastructure (OBI) endpoints. Authentication is HTTP Basic (the organization's authorization_token as the username with a blank password) or OAuth 2.0 client_credentials. Real-time notifications are delivered via outbound webhooks (HTTPS POST callbacks), not a WebSocket.
Credly publishes 5 APIs on the APIs.io network, including Badge Templates API, Events API, Issued Badges API, and 2 more. Tagged areas include Digital Credentials, Open Badges, Badging, Certifications, and Verifiable Credentials.
Credly’s developer surface includes authentication, documentation, and 8 more developer resources.
Kin Score
APIs 5
Individual APIs this provider publishes, each with its own machine-readable definition.
Credly Badge Templates API
Reusable credential designs badges are issued against.
Credly Events API
Organization event feed (mirrors webhook events).
Credly Issued Badges API
Badges issued to recipients from a badge template.
Credly OBI Recipients API
Open Badges Infrastructure endpoints for public verification.
Credly Organizations API
Organization details and employees directory.
Open Collections 1
Open, tool-agnostic API collections (OpenAPI-derived and Bruno).
Credly Web Service API
OPEN COLLECTIONPricing Plans 1
Published pricing tiers and plan structures.
Credly Plans Pricing
PLANSRate Limits 1
Documented rate limits and quota policies.
Credly Rate Limits
RATE LIMITSFinOps 1
Cost, billing, and metering signals for API financial operations.
Credly Finops
FINOPSSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Agentic Access 1
Recommended x-agentic-access execution contracts for AI agents.
Resources
Documentation 1
Reference material describing how the API behaves
Agent Surfaces 1
MCP servers, agent skills, and machine-readable catalogs
Access & Security 3
Authentication, authorization, and security posture
Operate 1
Status, limits, changes, and where to get help
Commercial 2
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API