Verifier API Quick Start

Step 01

Prepare your public record identifier.

HTTPS JSON interface

The Verifier API returns JSON over HTTPS. These examples use the current service host. Use the base URL agreed for your environment; a future public domain is not a different API contract.

Public data only

Approved preview records can resolve by public verify ID or public slug.

Your first lookup

Use a published verify ID or slug. Keep private workspace and device credentials out of public requests.

Step 02

Check the service state.

The health endpoint returns the API version, service status and verification capabilities for this interface.

GET/api/verifier/v1/health

Verifier preview health

Returns API version, service status and explicit false values for final verification, ledger anchoring and made by human certification.

Access: Public, no API key

shell

curl https://digibridge-home-pages.vercel.app/api/verifier/v1/health

200 response

{
  "ok": true,
  "apiVersion": "v1",
  "status": "preview",
  "service": "DigiBridge Verifier API",
  "finalVerificationActive": false,
  "ledgerAnchoringActive": false,
  "madeByHumanCertificationActive": false
}

Step 03

Resolve by a public identifier.

Pass either an active public verify ID or the approved public slug. URL encode user provided values before placing them in the query string.

GET/api/verifier/v1/resolve?code=<publicVerifyId_or_slug>

Resolve a Creation Record preview

Returns a public safe asset projection, shortened hash previews, optional proof summary and explicit trust boundary flags.

Access: Public, no API key

shell

PUBLIC_CODE="<publicVerifyId_or_slug>"
curl --get --data-urlencode "code=$PUBLIC_CODE" \
  "https://digibridge-home-pages.vercel.app/api/verifier/v1/resolve"

Step 04

Present the returned record status.

A successful lookup is a draft certificate preview. These fields are part of the current response contract and should remain visible anywhere the data is shown.

public preview response

{
  "ok": true,
  "apiVersion": "v1",
  "status": "public_preview",
  "verificationLevel": "draft_certificate_preview",
  "finalVerificationActive": false,
  "ledgerAnchored": false,
  "madeByHumanCertified": false,
  "asset": {
    "id": "<publicVerifyId>",
    "slug": "<publicSlug>",
    "title": "<approved public title>",
    "category": "film",
    "mediaType": "video",
    "creatorDisplay": "<approved display name>"
  },
  "proof": {
    "proofStatusLabel": "Public preview only",
    "certificateStatusLabel": "Draft certificate preview"
  }
}

This shortened response illustrates a film asset, not a film verification result. The full API reference describes optional summaries and release notices. Never treat an omitted field as a passed check.

Handle not found responses without record disclosure

Private and inactive records use the same generic response as an unknown identifier. Do not infer or expose whether another internal record exists.

Treat HTTP 404 as unavailable to the public
Do not retry with guessed private identifiers
Do not display internal record existence hints
Preserve the public preview labels on success

Step 05

Choose the next integration depth.

Read the API reference for endpoint details, or explore the device interfaces for signed event integration.

Open the API reference Review device interfaces

Make your first verifier request.