How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Didit Travel Rule API

The Travel Rule API from Didit — 11 operation(s) for travel rule.

Didit Travel Rule API is one of 17 APIs that Didit publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Travel Rule. The published artifact set on APIs.io includes an OpenAPI specification, an API reference, and API documentation.

This API exposes 14 operations across 11 paths, and defines 17 schemas. It is described by OpenAPI 3.0.0, at version 3.0.0.

Requests are made against a single base URL, https://verification.didit.me.

14 operations 11 paths 17 schemas 1 DELETE5 GET2 PATCH5 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
3.0.0
Base URL
https://verification.didit.me
Authentication
API Key, API Key, API Key
Resource Areas
1

Authentication & Security 3

Didit Travel Rule API declares 3 security schemes for authenticating requests. An API key is passed in the header as x-api-key (ApiKeyAuth). An API key is passed in the header as X-Transaction-Token (TransactionTokenAuth). An API key is passed in the header as Session-Token (SessionTokenAuth).

  • TransactionTokenAuth — Short-lived scoped token minted by your backend via POST /v3/transactions/sdk-token/. Used by the Didit SDKs on the device-facing /v1/transactions/ endpoints.
  • SessionTokenAuth — Short-lived token returned in the sessiontoken field of POST /v3/session/. Used by the hosted verification flow (and custom sandbox UIs) to call session-scoped…

Paths & Operations 14

Across 11 paths, the API surfaces 14 operations — 1 DELETE, 5 GET, 2 PATCH, 5 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Travel Rule 14
GET
/v3/travel-rule/settings/
Get Travel Rule settings
getTravelRuleSettings → 200
PUT
/v3/travel-rule/settings/
Update Travel Rule settings
updateTravelRuleSettings body → 200400
GET
/v3/travel-rule/wallet-addresses/
List wallet address book entries
listTravelRuleWalletAddresses 2 params → 200
POST
/v3/travel-rule/wallet-addresses/
Register a wallet address
createTravelRuleWalletAddress body → 201400
PATCH
/v3/travel-rule/wallet-addresses/{entry_uuid}/
Update wallet address holder metadata
updateTravelRuleWalletAddress 1 param body → 200
DELETE
/v3/travel-rule/wallet-addresses/{entry_uuid}/
Soft-delete a wallet address
deleteTravelRuleWalletAddress 1 param → 204
GET
/v3/travel-rule/vasps/
Search the VASP directory
listTravelRuleVasps 3 params → 200
PATCH
/v3/transactions/{transaction_id}/travel-rule/
Finish, cancel, or resend a Travel Rule transfer
patchTravelRuleTransfer 1 param body → 200400409
POST
/v3/transactions/{transaction_id}/travel-rule/ownership/
Confirm or deny wallet ownership
confirmTravelRuleOwnership 1 param body → 200409
GET
/v3/travel-rule/pickup/{token}/
Get email-rail pickup info
getTravelRulePickup 1 param → 200404410
POST
/v3/travel-rule/pickup/{token}/respond/
Respond to an email-rail pickup
respondTravelRulePickup 1 param body → 200404410
POST
/v3/travel-rule/inbound/
Register an after-deposit (sunrise) inbound transfer
registerTravelRuleInbound body → 200201
POST
/v3/travel-rule/widget-session/
Mint a wallet-ownership widget session
createTravelRuleWidgetSession body → 201
GET
/v3/travel-rule/widget/{token}/
Get wallet-ownership widget context
getTravelRuleWidgetContext 1 param → 200404410

Schemas 17

The contract defines 17 schemas that model the data the API accepts and returns. The most detailed are TravelRuleSettingsDetail (16 properties), TravelRuleSettingsUpdate (15 properties), TravelRuleTransferDetail (14 properties), TravelRuleWidgetContext (11 properties). Each schema is shown below with its type and property counts.

WalletAddressEntryCreate
object
7 properties 1 required
TravelRuleWidgetSessionCreate
object
8 properties 2 required
TravelRuleWidgetSessionResponse
object
4 properties
TravelRulePickupRespondRequest
object
2 properties 1 required
VaspDirectoryEntry
object
9 properties
TravelRuleTransferDetail
object
Full transfer object returned by the ownership-confirmation and finish/cancel endpoints. originatordata/beneficiarydata are omitted while PII is masked (see de…
14 properties
TravelRuleTransferPatchRequest
object
Provide exactly one of: paymenttxnid (finish), action=cancel, or action=resend.
2 properties
TravelRuleOwnershipConfirmRequest
object
1 property 1 required
WalletAddressEntry
object
10 properties
TravelRuleSettingsDetail
object
16 properties
TravelRulePickupInfo
object
5 properties
TravelRuleWidgetContext
object
11 properties
TravelRuleWidgetProofSummary
object
10 properties
WalletAddressEntryUpdate
object
PATCH is a partial update; the response echoes only holdername, holdervendordata, entitytype, and traveladdress.
4 properties
TravelRuleInboundRequest
object
8 properties 5 required
TravelRuleInboundResponse
object
4 properties
TravelRuleSettingsUpdate
object
All fields optional; PUT applies a partial update.
15 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

didit-travel-rule-api-openapi.yml Raw ↑

Other APIs Didit publishes across the network.

Didit Billing API
Didit Businesses API
Didit Case Blueprints API
Didit Cases API
Didit Customization API
Didit Questionnaires API
Didit Regulatory Reports API
Didit Report Templates API
Didit Session API
Didit Sessions API
Didit Standalone APIs API
Didit System API
Where this information came from

This is an independent, third-party profile of Didit Travel Rule API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.