Techinnoverz Verification API

Test and live keys

There is one base URL. The prefix of your key decides what happens: tz_test_ keys run against sample data, are never charged and never touch your wallet; tz_live_ keys run real checks and are charged. Live keys are issued once your account has been approved for live access.

Every response carries livemode, true for a live key and false for a test key.

A successful response also carries source and dataAsOf. source is "provider" when the data was fetched for your call, and "stored" when we answered a repeat of the same lookup from a record we kept of an earlier one; dataAsOf is when the data was fetched from its source. A result served from a kept record is billed the same as any other successful result.

Idempotency and retries

Send an Idempotency-Key header (1 to 128 letters, digits or . _ : -) with every check. Calling again with the same key and the same body returns the same result, marked with the Idempotent-Replayed: true header, and never charges twice.

If a call with the key is still running you receive 409 IDEMPOTENCY_IN_PROGRESS with a Retry-After header. The same key with a different body is 422 IDEMPOTENCY_KEY_REUSED. If an earlier attempt failed without charge (SOURCE_ERROR, SOURCE_TIMEOUT or a lost call), retrying with the same key runs the check again. Keys are remembered for 7 days.

Fetching a result again

Every response carries a txnId. GET /requests/{txnId} returns the stored response of that transaction, free of charge. If your connection dropped before you received a found result, fetching it (or retrying with the same Idempotency-Key) within 10 minutes delivers it and charges it once; a result you never fetch is not charged.

Stored responses are kept for 7 days. For Aadhaar, DigiLocker and credit-bureau checks they are kept for 10 minutes only.

Response headers

X-Request-Id repeats the txnId. RateLimit-Limit, RateLimit-Remaining and RateLimit-Reset describe your per-key limit, and Retry-After accompanies 409, 429 and 503 responses.

Timeouts and request size

A call that cannot finish within 30 seconds is answered with an error and is not charged. In the rare case that the result is found just after that, it can still be fetched with its txnId and is then charged once. Request bodies are limited to 64 KB, except checks that take photos (face match and face match with liveness), which accept up to 6 MB with JPEG or PNG images of up to about 2 MB each, base64 encoded. Images are never stored.