Skip to main content
This guide walks you through issuing an API key, ingesting a customer, and reading the result back.

1. Issue an API key

1

Open the Developers settings

Sign in to Instant Compliance and navigate to Settings → Developers. You will need the org.api-keys permission (Administrators have this by default; ask your Compliance Officer otherwise).
2

Create a key

Click Create key, give it a recognisable label (e.g. Zapier — HubSpot production), pick the scopes the integration needs, and click Create key.For an “ingest customers + read status back” integration: tick all three.
3

Copy the plaintext key

The key is shown once in the format ic_live_…. Copy it immediately into your integration’s secret manager. We will never be able to show it again — if you lose it, revoke the key and issue a new one.

2. Send your first request

Verify the key works by listing customers (returns an empty list if you have not ingested anyone yet):
You should receive { "object": "list", "data": [], "has_more": false, "next_cursor": null, "limit": 50 }.

3. Ingest a customer

Response (201 Created):
No KYC is triggered and no credits are charged. The customer record is created so your back-office team can review it, complete the risk questions, and start verification from inside Instant Compliance.

4. Read status back

Once your compliance team has verified the customer, poll for the result. Use updated_since so each poll only returns records that changed since the previous run:
When kyc_status becomes VERIFIED and aml.status becomes CLEAR, the customer is fully cleared. See Customer lifecycle for the full state machine.

Next steps

Upsert by external_id

The right way to wire create-or-update from your CRM.

Polling for status

Get a robust polling loop right the first time.

Zapier integration

No-code recipe for HubSpot, Pipedrive, Salesforce, etc.

Idempotency

Make every retry safe.