Emblem Connect Overview

Emblem Connect is Emblem's partner integration surface for verification providers. It lets you add an "Already verified with Emblem?" branch to your existing flow and, after your own verification succeeds, offer the user an opt-in path to create an Emblem pass for future reuse.

Who it's for

These docs are for provider engineers building inside an existing verification product.

If you're a publisher adding age verification to your site, use the main docs instead.

Two flows

Assertion

Use assertion when you want to check whether the user already has an Emblem pass that satisfies your policy.

• If reusable proof exists, your server receives assertion data after code exchange.
• If reusable proof does not exist, Emblem redirects back with a clear requires_verification outcome and you continue your normal verification flow.

Enrollment

Use enrollment after your own verification succeeds and the user explicitly opts in to creating an Emblem pass.

• Your server records verification provenance and starts enrollment in one call.
• The user creates a passkey on Emblem and returns to your redirect_uri.

Typical integration sequence

Most providers start with assertion because it is the smaller contract:

1. Create assertion transactions.
2. Handle the browser callback.
3. Exchange approved codes on the server.
4. Add reconciliation for interrupted flows if needed.

Enrollment is usually added second, once you want to convert successful provider verifications into reusable Emblem passes.

You do not need both flows to start.

Prerequisites

Before you integrate either flow, you need:

• An Emblem publisher account.
• A provisioned authorization client (client_id).
• One or more registered redirect_uri values on that client.
• A secret API key (emb_sk_...).

Authorization clients are provisioned by Emblem during partner onboarding. They are not self-serve today.

Authority model

Connect has two separate authorities:

• Assertion authority lets you check for existing reusable proof.
• Enrollment authority lets you create new Emblem passes after your own verification succeeds.

Being approved for assertion does not automatically mean your client can start enrollment. Enrollment requires separate credential issuance authority on the same client_id.