Developer API
Integrate predictable, versioned JSON endpoints for organization requests and authenticated mobile verification flows.
Environment
Organization keys are explicitly scoped to test or live mode. Rotating one environment never changes the other.
Authentication
Organization request creation uses `X-API-KEY`. Mobile user flows use `Authorization: Bearer TOKEN`. The two are intentionally never interchangeable.
Verification lifecycle
The API handles request creation, user consent, event delivery, and completion without blurring authentication boundaries.
Create a verification with an organization API key, target email, address, and duration.
The authenticated user retrieves the request and explicitly accepts or rejects it.
A verification-scoped tracking token authorizes idempotent geofence events.
The organization reviews a stable verification outcome and audit summary.
Simple integration
Every API response returns a `data` object and an `error` field, giving clients one stable parsing strategy across success and failure cases.
POST /api/v1/verificationsX-API-KEY: sk_test_...Content-Type: application/json{ "email": "person@example.com", "address": "10 Market Street", "tracking_days": 2}201 CreatedAPI guarantees
Bearer tokens expire after 30 days and can be revoked without affecting unrelated sessions.
Generic authentication errors and request throttling reduce account enumeration and abuse.
Verification-scoped identifiers make retries safe when mobile connectivity is unreliable.
Build trust by design
Request test credentials and discuss the right integration path for your verification workflow.