Reference implementations

Explore complete UnifyID integrations

Run three production-shaped applications that demonstrate Hosted UnifyID, the UnifyID component, and direct OAuth API integration from authorization through approved identity access.

Choose a reference application

Each application is a separate repository with its own interface, product use case, backend, OAuth transaction handling, application session, tests, and local setup instructions. The demos use real UnifyID authorization data; they do not fabricate approved identity claims.

Hosted UnifyID

NovaCampus

An international scholarship marketplace that uses verified identity, nationality, age assurance, and document summaries to simplify eligibility checks.

unifyid-demo-novacampus

UnifyID component

TrustHire

A verified talent marketplace where candidates create a consented identity passport and apply to high-trust roles through the popup component flow.

unifyid-demo-trusthire

OAuth API

AtlasRemit

A cross-border account experience demonstrating direct OAuth control, approved documents, country discovery, protected actions, and signed webhooks.

unifyid-demo-atlasremit

What each demo proves

Capability	NovaCampus	TrustHire	AtlasRemit
Integration mode	Hosted redirect	Web component popup	Direct OAuth API
State, nonce, and PKCE	Server managed	Component transaction + backend	Server managed
Token exchange	Backend	Backend	Backend
UserInfo	Yes	Yes	Yes
Document summaries	Yes	Not required by use case	Yes
Country capability discovery	Not required by use case	Not required by use case	Yes
Signed webhooks	Lifecycle-ready pattern	Lifecycle-ready pattern	Complete receiver
Local port	`4101`	`4102`	`4103`

Connect a demo to the deployed Sandbox

The UnifyID services are already deployed. Only the reference application runs on localhost. Create separate application credentials for each demo instead of copying credentials between repositories.

1Sign in to the deployed UnifyID Developer portal
2Create a separate confidential Sandbox application for the demo
3Register the demo’s exact callback URI
4Enter accurate application information and select only the scopes required by that repository
5Create an OAuth Client Secret and copy it when it is displayed
6Configure a signed webhook endpoint when the demo requires lifecycle events
7Copy .env.example to .env and add credentials from your own application
8Install dependencies, run the checks, and start the local demo
9Complete Continue with UnifyID using a real Sandbox account

Demo	Registered callback	Start
NovaCampus	`http://localhost:4101/auth/callback`	`cd unifyid-demo-novacampus && npm install && npm start`
TrustHire	`http://localhost:4102/auth/callback`	`cd unifyid-demo-trusthire && npm install && npm start`
AtlasRemit	`http://localhost:4103/oauth/callback`	`cd unifyid-demo-atlasremit && npm install && npm start`

All three demos use https://api.dev.unifyid.io. Their localhost URLs are developer-owned callbacks only. Set UNIFYID_CLIENT_ID and UNIFYID_CLIENT_SECRET from the application you created before starting a demo. AtlasRemit additionally requires UNIFYID_WEBHOOK_SECRET for its signed webhook receiver.

Do not hard-code credentials, reuse another application's Client ID, expose a Client Secret in browser code, or point an UnifyID service URL to localhost. Production domains and credentials are provided only after Production review and approval.

Production boundary

The demos are integration references, not deploy-without-review templates. Before Production, use Redis or a database for OAuth transactions and sessions, HTTPS Secure cookies, managed secrets, discovery/JWKS token validation, durable webhook idempotency, data retention controls, and application-specific authorization.

Continue building

Start with NovaCampus for the smallest secure integration surface, TrustHire when you need an embedded entry point, or AtlasRemit when your backend needs complete transaction and webhook control.