Changelog

What changed, and when

Every change to the Emnet API, SDKs and platform. Breaking changes to a released API version are announced in advance, never shipped quietly.

Service status

A live status page with historical uptime is in progress. Until it ships, incidents are announced by email to affected accounts and support@emnetid.com is the fastest route to a human.

Our compatibility promise

Within a released API version we will add optional fields and new endpoints, but we will not remove a field, change a type, or tighten validation on an existing one. Treat unknown fields as additive — the SDKs already ignore them — and you will not be broken by an Emnet release.

Releases

Emnet Identity API v1 — early access

The v1 API contract is published. Early access is by request — write to sales@emnetid.com — and your base URL is issued with your early-access key. The date live verification against Fayda opens will be announced on this page. The public API is versioned at /v1 and covered by our compatibility commitment: no breaking change to an existing v1 endpoint without a new version and advance notice.

  • GET /v1/verification/person/fayda/authorize-url — start a verification
  • POST /v1/verification/person/fayda/callback — exchange the code for claims
  • GET /v1/verification/person/session/{id} — read a session’s status

Official Java SDK

A typed client with no framework dependencies — java.net.http.HttpClient and Jackson only, so it drops into a Spring, Quarkus or plain-Java service without a version fight. See the SDK guide.

Publishable keys and tiered rate limits

Publishable (pk_) keys can start a verification from a browser or mobile client but cannot retrieve claims — the claims endpoint accepts secret keys only. Rate limits apply per key, with a tighter ceiling for publishable keys; throttled responses carry Retry-After. See rate limits.

Developer dashboard — in development

A self-serve dashboard to sign up, mint and revoke API keys, and see usage per key follows at general availability. Until then, early-access keys are requested by e-mail. Either way, a key is shown once at creation and stored only as a hash — if one is lost, it is revoked and replaced.