Authenticate to the Credly API using the credentials provided in your Credly account; all requests must include the appropriate authorization header and set Content-Type to application/json
Retrieve the badge template identifier for the badge type you wish to issue from your organization's templates via the templates endpoint
POST to the issued badges endpoint with the recipient's email, the badge template identifier, and any optional metadata (expiration, evidence URLs) to issue the badge; handle a 422 response by inspecting the returned validation errors
To list all issued badges for an organization, GET the issued badges collection endpoint; the API returns at most 50 results per page, so iterate using the page query parameter until no further results are returned
For bulk retrieval, use the bulk badges endpoint if available in your plan tier rather than paginating through the standard collection endpoint
Known gotchas
The platform was formerly known as Acclaim; legacy API base URLs (youracclaim.com) may still appear in older integrations and documentation but the canonical base is credly.com
A 422 Unprocessable Entity response contains a structured list of field-level validation errors; surfacing these to the caller is essential because generic error handling masks actionable problems like an invalid email format or an inactive badge template
Badge issuance to a recipient who already holds the same badge template may be silently accepted or rejected depending on your organization's duplicate settings; verify the org-level policy before building automated bulk 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