issue an Open Badge to a recipient using the Badgr API badge-class award endpoint
domain: badgr.com · 5 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Set up a developer API key and obtain an OAuth2 access token for the Badgr account
Identify or create the target Badge Class within an existing Issuer
POST an assertion request to the badge class's award endpoint with the recipient's identity (typically a hashed email) and issue date
Retrieve the resulting assertion and baked badge image URL to deliver to the recipient
Verify the assertion is publicly resolvable and validates against the Open Badges verification process
Known gotchas
Badgr.io no longer accepts a custom slug when creating a badge class via the API — it auto-assigns a UUID-based slug, which breaks integrations that hardcoded predictable slugs
Badgr is now part of Instructure/Parchment; confirm the current API base host and product name before wiring up new integrations, since branding and hosting have changed
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?