Skip to main content
The AMLOK API organizes authorized financial evidence into a common data model and coordinates verification, underwriting, monitoring, and analytical investigation workflows. AMLOK identifies changes and risk signals so your institution can decide when to intervene. Borrower outreach and intervention take place in your institution’s own systems. This reference contains 192 operations, 63 financial-data resource types plus credit and billing reporting resources, 27 event types, and schema-checked example payloads. Endpoint pages include cURL, Python, and Node.js request examples, response bodies, required scopes, and error definitions.

Make your first request

Follow a complete connection and data-read flow.

Authentication and scopes

Understand API keys, workspace boundaries, and permissions.

Webhooks

Verify signatures, deduplicate deliveries, and process changes.

OpenAPI and examples

Download the specification, Postman collection, and verification code.

​
How the API fits together

  1. Create or identify a business or person under your institution tenant.
  2. Record actual authorization and connect an enabled provider.
  3. Synchronize evidence and read normalized records with their coverage and provenance.
  4. Start approved workflows and retrieve asynchronous results.
  5. Process signed events and keep your local records in sync.
Financial-data and reporting operations use a server-side bearer API key. The healthcheck and service-status endpoints are public and require no key. Each key authorizes exactly one workspace. Resources are workspace-scoped; a resource ID alone never grants access. Source capabilities, consent, scopes, and field entitlements all constrain the returned data.

​
Explore the API

​
Version and availability

Use the integration status catalog to check provider availability and supported markets. Returned resources and fields depend on your enabled products, source permissions, and account entitlements. This reference covers AMLOK API 1.4.2. Endpoint paths use the /v1 major-version namespace. Configure AMLOK_API_BASE_URL with the environment URL issued to your institution. See integration onboarding for environment setup and versioning for compatibility rules. Your account manager provides client portal access information. Authorized administrators create workspace-bound API keys in the portal. Start with configuration discovery and sandbox journeys.