Early integration partners

Ask for an answer, not for a copy.

Sign in with Unidy. Read a field you were given permission to read. Request only what you need and keep no more than you must.

Unidy lets a person keep their own information and decide who may read it. Your product asks for an answer instead of storing another copy. Access for other organisations is in development with a first group of integration partners: write to partners@unidy.com to join.

What you will be able to integrate

  • “Link my Unidy”: sign-in through a standard OpenID Connect provider.
  • You receive the person’s name and Unidy ID, never their email address: you reach them through Unidy.
  • Permission to read specific fields, for a stated purpose and period.
  • Verified answers, such as “over 18”, without the document behind them.
  • The current value of a detail, instead of a copy that goes stale.

Standard sign-in, not a new protocol

Unidy runs its own OpenID Connect provider at id.unidy.com, which already signs people in to Unidy’s own apps. For your product it will be another issuer, discovered the usual way, with the authorisation code flow and PKCE. Relying parties hard-code an issuer, so it stays put.

What is not here yet

No client registration for other organisations, no sandbox, no SDKs and no scope catalogue. When there is something to build against, it will be documented here: a quickstart, an API reference and examples.

Join the integration programme

Tell us what your product asks customers for today, and what you would rather not store. Write to partners@unidy.com.