Developer center

Contract-led integration.
Context-bound decisions.

For vendors, development teams and integration partners. Every API links to its service, context and evidence.

From purpose to go-live criteria

Select an endpoint to inspect its input, response and access requirements.

API	Purpose	Model
`POST /enrollments`	Bind a reference to an authoritative record after processing-basis checks.	Draft
`POST /identify`	Resolve identity within an authorized population.	Draft
`POST /verify`	Compare a palm with the claimed identity.	Draft
`POST /presence`	Record presence after session and device checks.	Draft
`POST /authorizations`	Evaluate action permission separately from biometric matching.	Draft
`GET /evidence/{id}`	Retrieve an authorized event, not a biometric template.	Draft

Simulate decisions and errors with synthetic fixtures.

Define the roles of HIS, SIS, HRM and ACS.