Developer Preview

The endpoints, curl examples and embed snippet on this page are illustrative — the Credential API is not yet live. Public credential verification already works at /verify.

The Verified Credential API

Every completed RogueBoard project becomes a portable, verifiable credential — not a badge image, but a data object any platform can request, check, and embed. Built for employers, ATS platforms, portfolio sites, and partner integrations.

Overview

Why this is more than a badge

Most "digital badges" are just an image with a claim attached. The RogueBoard Verified Credential API returns a structured, checkable record for every completed project — so a hiring manager, an ATS, or a portfolio site can verify it in one request instead of taking a screenshot on faith.

Project ID

The unique code of the completed project, e.g. #H9DPU.

Project Title

The full name of the project as listed on RogueBoard.

Completion Status

Whether the project was fully completed, partially completed, or withdrawn.

Skills Demonstrated

The specific skills tagged to that project and role.

Evidence Links

Direct links to the deliverables produced — files, repos, documents.

Mentor Verification

Confirmation of who signed off on the work and when.

Completion Date

The date the project was formally closed out.

Credential ID

A unique, permanent ID for this specific credential, e.g. RB-10482.

Public Verification URL

A shareable link anyone can open to confirm the credential is real.

Live Example

What a credential looks like

Every credential renders the same way whether it's viewed on RogueBoard, embedded on a personal site, or pulled into a partner platform via the API.

✓
Verified RogueBoard Credential
#RB-10482
Brand Identity for a Local Café Chain
Completed12 September 2026
Verified byProject Manager
SkillsBranding, Graphic Design
Same credential, as JSON
{ "credential_id": "RB-10482", "project_id": "H9DPU", "project_title": "Brand Identity for a Local Café Chain", "completion_status": "Completed", "skills_demonstrated": ["Branding Concepts", "Graphic Design"], "evidence_links": [ "https://rogueboard.co.uk/evidence/RB-10482/logo-files", "https://rogueboard.co.uk/evidence/RB-10482/guideline-pdf" ], "mentor_verification": { "verified": true, "verified_by": "Project Manager", "verified_on": "2026-09-12" }, "completion_date": "2026-09-12", "public_verification_url": "https://rogueboard.co.uk/verify/RB-10482" }

API Key

Your development key

Every RogueBoard account gets a sandbox API key for testing integrations. Below is a sample — real keys are issued once the API leaves developer preview.

rb_test_EXAMPLE_KEY_REQUEST_YOURS

Sandbox keys are rate-limited and only return sample data like the example above. Never share a live key publicly or commit it to a public repository.

Quick Start

Fetch a credential

curl https://api.rogueboard.co.uk/v1/credentials/RB-10482 \ -H "Authorization: Bearer rb_test_EXAMPLE_KEY_REQUEST_YOURS"

Returns the JSON object shown above. No authentication is required for the public verification endpoint — see Endpoints below.

Embed Widget

Drop a credential onto any website

Paste this snippet anywhere on a page — a portfolio site, a CV page, an agency profile — and it renders the live, verified credential card shown below.

<div id="rogueboard-credential"></div> <script src="https://cdn.rogueboard.co.uk/widget.js" data-credential="RB-10482" data-key="YOUR_API_KEY"> </script>
Rendered output
✓
Verified RogueBoard Credential
#RB-10482
Brand Identity for a Local Café Chain
Completed12 September 2026
Verified byProject Manager

Endpoints

API reference

MethodEndpointDescription
GET/v1/credentials/{credential_id}Retrieve a single credential by its ID. Requires an API key.
GET/v1/users/{user_id}/credentialsList every credential earned by a specific user. Requires an API key with user consent scope.
GET/v1/verify/{credential_id}Public verification lookup — confirms a credential is genuine. No authentication required.
POST/v1/webhooksRegister a webhook to be notified when a new credential is issued. Planned for general availability.

Authentication & Limits

Before you integrate

  • All authenticated requests use a Bearer token in the Authorization header.
  • The public verification endpoint (/v1/verify/{credential_id}) never requires a key — anyone should be able to check a credential is real.
  • Sandbox keys are limited to 100 requests/hour and only return sample data.
  • Listing a user's full credential history requires that user's explicit consent — RogueBoard will never expose a participant's credentials to a third party without it.
  • This API is in developer preview. Endpoints, fields, and rate limits may change before general availability.

Want early access to the API?

We're onboarding a small group of partners ahead of general availability.

Request Early Access →