Authenticate to the Credly API using OAuth 2.0 with your organization's client credentials to obtain an access token
Ensure the badge template (badge definition) exists in Credly's platform with the correct badge_template_id representing the achievement to be awarded
POST /v1/organizations/{org_id}/badges with earner email, badge_template_id, issued_at timestamp, and optionally evidence URLs to issue the badge
Credly generates the Open Badge 3.0 credential as a JSON-LD VerifiableCredential and sends an email notification to the earner
The earner accepts the badge via Credly's platform; retrieve the badge record via GET /v1/organizations/{org_id}/badges/{badge_id} to confirm accepted status
Optionally call the Workforce API endpoint to retrieve issued badge data for organizational reporting or LMS credit awarding
Known gotchas
Credly's API issues badges in Open Badge 3.0 format with an underlying VC Data Model structure, but verification URLs and wallet delivery depend on the earner accepting through Credly — third-party wallet portability via BadgeConnect requires the earner to initiate the transfer
Badge issuance to an email address that has no Credly account creates a pending badge; it only becomes accepted after the earner registers — design downstream workflows to handle the pending state
Revocation via the API (DELETE /v1/organizations/{org_id}/badges/{badge_id}) immediately invalidates the public badge URL and VC proof — irreversible; create test badges against a sandbox organization to verify logic before production issuance
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp