Skip to main content
POST
Python

When to use it

Use it when a deposit from List unmatched deposits has a received Travel Rule message that belongs to it and Didit did not pair the two on its own. The deposit takes the message’s originator data, counterparty VASP and rail, and both transfers record the match on their timelines.

Request

Notes

  • transaction_uuid in the path is the deposit. transaction_id in the body is the message.
  • The message must be for the same asset as the deposit.
  • The call fails with 409 when either side has already moved on, and changes nothing.
  • A transaction deleted from the Console answers 404, on either side.

Authorizations

x-api-key
string
header
required

Your application's API key, from Developers -> API keys in the Business Console. The primary key has full access. A named key can be scoped: none, read or write per resource, limited to some workflows or to approved sessions, to a list of IP addresses, and to an expiry date. 401 means the key is wrong, revoked or expired; 403 means no key was sent, the key has no access to this resource or action, or the request came from an address outside its IP list; 404 on a session route means the session is outside the key's workflows or statuses. A key without media access receives image, video and PDF URLs as null, and a key without sessions write receives session links and tokens as null. See https://docs.didit.me/console/api-keys.

Path Parameters

transaction_uuid
string<uuid>
required

The transaction_id of the unmatched deposit.

Body

application/json
transaction_id
string<uuid>
required

The transaction_id of the received Travel Rule message (a row with kind: message).

Response

Both transfers after the match.

deposit
object
required

One Travel Rule transfer as the transfers list shows it: VASP names, wallets and memos only, never the originator or beneficiary person data.

message
object
required

One Travel Rule transfer as the transfers list shows it: VASP names, wallets and memos only, never the originator or beneficiary person data.

Last modified on October 31, 2026