Didit Transaction Monitoring & Travel Rule API

Didit Transaction Monitoring & Travel Rule API

Overview

Scores every transaction in real time against a rule engine (conditions, velocity windows, blocklists), screens crypto wallets and transaction hashes against blockchain analytics, and runs the FATF / EU TFR Travel Rule exchange with counterparty VASPs.

Key facts:

• POST /v3/transactions/ is synchronous: screening, Travel Rule routing and rules all run inside the call, so the 201 response already carries the verdict. A transaction is created APPROVED; rules may move it to IN_REVIEW, DECLINED or AWAITING_USER.
• transaction_id is unique per application. Reusing it is rejected (400 with {"transaction_id": "A transaction with this transaction_id already exists."}, or 409 when two requests race); the existing transaction is never returned. After a timeout, treat that 400 as "already created" and find the record in GET /v3/transactions/ instead of resubmitting.
• GET /v3/transactions/{uuid}/ takes Didit's uuid from the create response, not your transaction_id.
• Sandbox applications store transactions but skip rules, crypto screening, webhooks and billing (they stay APPROVED).
• Non-monetary activity (logins, gameplay, bonuses, chargebacks) goes to the events API: see the didit-event-monitoring skill.

Pricing: $0.02 per transaction (Transaction Screening); a Travel Rule transfer is billed $0.02 per outbound transfer on its own line instead of the screening fee, never both; Wallet Verification & Screening (transaction-coupled or on-demand) from $0.15 with Didit-managed analytics, $0.02 with your own provider key, charged once even when Travel Rule attribution needs the same lookup. Sandbox is never billed. These are the list prices until 1 November 2026, when Didit pricing changes and the 500 free checks a month become $10 of free credit a month. Check didit.me/pricing for current prices.

API Reference: https://docs.didit.me/management-api/transactions/create Feature guides: https://docs.didit.me/transaction-monitoring/overview | https://docs.didit.me/transaction-monitoring/rules-api | https://docs.didit.me/transaction-monitoring/travel-rule | https://docs.didit.me/transaction-monitoring/wallet-screening

Authentication

Every request needs the x-api-key header. Use your application's API key from the Didit Business Console under Developers > API keys, or create an account and key programmatically (see Getting Started). Named keys with custom access need Transactions access (read for GET, write for POST, PUT, PATCH and DELETE); a key limited to some workflows or to approved sessions cannot have Transactions access.

Two exceptions: GET /v3/travel-rule/widget/{token}/ takes no key (the token is the credential), and the device endpoints /v1/transactions/ authenticate with X-Transaction-Token (see SDK transaction tokens).

Getting Started (No Account Yet?)

If you don't have a Didit API key, create one in 2 API calls:

1. Register: POST https://apx.didit.me/auth/v2/programmatic/register/ with {"email": "[email protected]", "password": "MyStr0ng!Pass"}
2. Check email for a 6-character verification code
3. Verify: POST https://apx.didit.me/auth/v2/programmatic/verify-email/ with {"email": "[email protected]", "code": "A3K9F2"}. The key is in the response at application.api_key.

To add credits: GET /v3/billing/balance/ to check, POST /v3/billing/top-up/ with {"amount_in_dollars": 50} for a Stripe checkout link.

See the didit-verification-management skill for full platform management (workflows, sessions, users, billing).