canonical: https://jentic.com/apis/mitekcloud.com/mitekcloud

# Mitekcloud Mitek Identity Cloud API

The Mitek Identity Cloud API runs identity verification, document data extraction, biometric enrollment, and AAMVA driver licence checks for KYC and onboarding flows. It bundles Mobile Verify for document and selfie verification, Mobile Fill for OCR-driven data prefill, MiPass for biometric enrolment and match, and a face blocklist for blocking returning fraudsters. OAuth-style token issuance is handled by `/connect/token`, with verification calls under `/api/verify`, `/api/fill`, `/api/biometric`, and `/api/blocklist.`

## For AI agents

Run document and biometric identity verification, extract structured data from IDs, and check faces against a blocklist via Mitek's KYC platform. Issues OAuth tokens and supports AAMVA driver licence checks.

## Scope

Does not handle credit checks, AML screening, or business KYB - use for document, biometric, and AAMVA identity verification only.

## Capabilities

- Run document plus selfie identity verification with Mobile Verify
- Extract structured data from photographed IDs with Mobile Fill
- Enrol and verify users biometrically through MiPass
- Add and query faces against the fraud blocklist
- Issue OAuth access tokens for downstream verification calls
- Run AAMVA driver licence checks for US ID validation

## Use cases

### KYC Onboarding Flow

New customer signups capture a government ID and a selfie, and the Mitek API confirms the document is genuine, the face matches the photo on the document, and the data fields are consistent. The verification dossier endpoint orchestrates these checks in one call so the onboarding system gets a single pass or fail decision plus extracted personal data for account creation.

Example prompt: Submit a verification dossier with a passport image and selfie via POST `/api/verify/v2/dossier` and parse the decision and extracted fields

### Returning Fraudster Detection

Maintain a blocklist of faces from confirmed fraud cases, then on every new application check the applicant's selfie against the list before any other verification step. The biometric endpoint returns a match score with metadata so the orchestrator can decline the application immediately and avoid wasting downstream verification budget.

Example prompt: Add the confirmed fraud applicant's face to the blocklist via POST `/api/blocklist/v2/items` and re-run the next applicant's selfie against it

### Form Prefill from ID Photo

Reduce signup form friction by letting the user photograph their ID card, then call Mobile Fill to extract name, address, date of birth, and document number. The structured fields populate the form and the user only confirms or corrects them, cutting completion time without losing data quality.

Example prompt: Call POST `/api/fill/v2/document` with a driver licence image and map the returned fields to the user signup form

### Agent-Mediated Verification via Jentic

An onboarding agent discovered through Jentic can call the dossier endpoint, branch on the verification decision, and trigger downstream actions like account creation or manual review queueing. Jentic isolates the bearer token in the credential vault so the agent never sees the raw secret used to call Mitek.

Example prompt: Use Jentic to find the Mitek verification dossier operation, execute it with applicant images, and route the case based on the decision field

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/connect/token` | Issue an OAuth access token |
| POST | `/api/verify/v2/dossier` | Run a full document and selfie verification |
| POST | `/api/fill/v2/document` | Extract fields from an ID image |
| POST | `/api/biometric/v2/enrollments` | Enrol a face for MiPass |
| POST | `/api/biometric/v2/verify` | Verify a selfie against an enrolment |
| POST | `/api/blocklist/v2/items` | Add a face to the fraud blocklist |

## Key resources

- **verify** — Mobile Verify document and selfie verification dossiers
- **fill** — Mobile Fill OCR data extraction from IDs
- **biometric** — MiPass biometric enrolment and verification
- **blocklist** — Face blocklist for known fraud actors
- **connect** — OAuth token issuance

## Why Jentic

- **Setup:** Wiring Mitek by hand means exchanging client credentials at `/connect/token` for a bearer token, targeting the US host (api.us.mitekcloud.com), and coding the dossier, biometric, and blocklist calls yourself. Through Jentic you install once, import Mitek Identity Cloud from the API Directory, store the credentials once, and your agent calls it.
- **Permission scoping:** Mitek's verify, fill, and biometric endpoints carry their payload in the request body rather than a URL path resource, so scope the agent to the operations it needs, such as running a document check or a biometric verify. You choose which operations are allowed, so adding a blocklist item is only included if you add it.
- **Credential handling:** Your Mitek client credentials and issued bearer token are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'verify customer identity' or 'run a document check', and Jentic returns the matching Mitek operation with its input schema and example payload so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Onfido API** — Document and biometric identity verification platform
- **Sumsub API** — KYC, KYB, and AML verification platform
- **Auth0 Management API** — User account and authentication management

## FAQ

### What authentication does the Mitek Identity Cloud API use?

The API uses bearer token authentication. Tokens are issued from POST `/connect/token` using your client credentials and passed in the Authorization header on subsequent calls. Through Jentic the bearer token is held in the credential vault and injected at execution time.

### Can I extract data from a driver licence with the Mitek API?

Yes. Use the Mobile Fill endpoint at POST `/api/fill/v2/document`, posting the licence image. The response returns extracted fields such as name, address, date of birth, and document number ready to populate a signup form.

### What are the rate limits for the Mitek Identity Cloud API?

Mitek applies per-tenant request limits that depend on your contract. Verification dossier calls are typically capped at a lower rate than token issuance. Check your Mitek customer portal for the current numeric quotas before running batch backfills.

### How do I run a full KYC check through Jentic?

Search Jentic for verify identity dossier, load the schema for POST `/api/verify/v2/dossier`, and execute with the applicant's document image and selfie. The structured response includes a decision and the extracted document fields for downstream account creation.

### Does the Mitek API support biometric face matching?

Yes. The MiPass endpoints under `/api/biometric/v2` enrol a user's face and then verify a new selfie against that enrolment. You can also check faces against the fraud blocklist via `/api/blocklist/v2/items.`

### Can the Mitek API verify US driver licences against AAMVA?

Yes. The verification dossier supports AAMVA-backed checks for US driver licences as part of the verify flow. The decision response indicates whether the AAMVA component passed alongside document and biometric results.

### Can I limit what my agent is allowed to do with the Mitek Identity Cloud API?

Yes. Because you run Jentic One yourself, your own rules decide which Mitek operations the agent may call and which credentials it may use. You can allow only the operations you need, such as running a document and selfie verification at POST `/api/verify/v2/dossier` or extracting ID fields at POST `/api/fill/v2/document`, while withholding others. Since these calls carry their payload in the request body rather than a URL path, adding a face to the fraud blocklist at POST `/api/blocklist/v2/items` is included only if you explicitly grant it.