Verify Badge Assertion
Changed onPublic endpoint — no authentication required. Any user (logged in or not) may check verification status of a badge assertion.
Verify a badge assertion against Open Badge criteria. Each failed criterion adds a key to reasons, and verified is true only when there are none:
- status: the assertion is Claimed.
- issue_date: an issue date exists and is not in the future.
- provider: for a Navigatr-issued badge, the provider exists and is verified; for an imported badge, the issuer record exists and has a source URL.
- recipient_name: for a Navigatr-issued badge, the recipient name matches the linked account (fuzzy); for an imported badge, a recipient identifier in the credential matches one of the importer's verified emails.
- source (imported badges only): the source still verifies, by re-fetching the hosted assertion (OB 2.0) or re-checking the signature and revocation status (OB 3.0).
- time_claimed: a claim date exists and is not in the future. It is not compared with the issue date, which the issuer supplies.
- time_updated: if the assertion has been updated, the update is not before the claim.
- end_date: the assertion has not passed its expiry date.
time_verified reflects the current state: set when all criteria pass and cleared when any fail. The exception is an imported badge whose only failure is a non-definitive source result (for example, the source is unreachable), which leaves it intact. The website renders a green tick next to the recipient avatar while it is set, so the flag must follow the live verification result rather than stick on the first success.
Returns 403 for non-public assertions (e.g. Pending).
Request
- Base URLhttps://api.navigatr.app (the document declares no server; this is the origin it was published from)
- Authnone declared
- TypeScriptA function with typed inputs. Its response is checked against the schema.
Path parameters
Response
Successful Response
Changes
- info
endpoint added
- info