SDK Availability | DigiBridge

Use the HTTP client you already know.

The Verifier API uses HTTPS and JSON. The examples below work with standard JavaScript and Python clients, so you can connect without an additional package.

Integration note: There is no official public DigiBridge SDK listed for this interface. Use the HTTP examples below. They retrieve a record; they do not install a recorder or run the verification agent.

Client options

Choose a client for your platform.

HTTPS and JSON

Any standards compliant HTTP client can call the public Verifier API preview.

JavaScript

Use fetch to resolve a public identifier, handle errors and read the response status.

Python

Use an HTTPS client to retrieve JSON and handle unavailable records before processing the result.

Current integration

Use your platform's native HTTP client.

The current interface uses ordinary GET requests and JSON responses. Examples use the current service host; use the base URL agreed for your environment. No additional client package is necessary.

browser or Node.js

const code = encodeURIComponent(publicVerifyIdOrSlug);
const response = await fetch(
  "https://digibridge-home-pages.vercel.app/api/verifier/v1/resolve?code=" + code,
  { headers: { Accept: "application/json" } }
);

if (response.status === 404) return null;
if (!response.ok) throw new Error("Verifier API preview failed");

const preview = await response.json();

Python standard library

import json
from urllib.error import HTTPError
from urllib.parse import quote
from urllib.request import urlopen

code = quote(public_verify_id_or_slug, safe="")
url = f"https://digibridge-home-pages.vercel.app/api/verifier/v1/resolve?code={code}"

try:
    with urlopen(url, timeout=15) as response:
        preview = json.load(response)
except HTTPError as error:
    if error.code == 404:
        preview = None
    else:
        raise

Client design

What to expect from a client integration.

Typed public responses

Discriminated success and not found models with explicit preview trust flags.

Version and retry policy

Handle non success responses explicitly, avoid unlimited retries and check the documented version before changing a client.

Presentation helpers

UI neutral helpers that preserve preview and draft labels instead of promoting status.

Enterprise authentication

Use the public endpoint without credentials. Agree any organisation access requirements directly with DigiBridge.

Supply chain safety

Package names are not proof of publisher identity.

Before installing a client package

Confirm the package is linked from this documentation
Verify the publisher and integrity metadata
Pin a reviewed version in production
Review permissions and network behaviour
Do not paste workspace or device secrets into examples
Treat all currently unlisted packages as unofficial