> ## Documentation Index > Fetch the complete documentation index at: https://docs.didit.me/llms.txt > Use this file to discover all available pages before exploring further. # List Related Transactions > List the other transactions in your application that share a party vendor_data with a monitored transaction, newest first and paginated. List Related Transactions API Prompt Copy prompt to clipboard \

\`List the transactions related to one Didit monitored transaction through the Management API.

Endpoint:
GET https://verification.didit.me/v3/transactions/{transaction_id}/related/

Authentication:
Use the x-api-key header with my Didit API key. A scoped key needs transactions: read. Keys limited to specific workflows or to approved sessions cannot call this endpoint.

Goal:
\- See the other transactions that involve the same people or companies as this one (same applicant, or this transaction's counterparty appearing elsewhere) so I can review a transaction in context.

Path parameter:
\- transaction_id: the Didit transaction uuid, not my own txn_id.

Behavior:
\- A transaction is related when one of its parties, in any role, has the same vendor_data as one of this transaction's parties. Matching uses vendor_data only, within my application.
\- The transaction itself is never returned. Parties without vendor_data are ignored, so if none of this transaction's parties has a vendor_data the result is always empty.
\- Ordered by txn_date, newest first, then created_at.
\- Paginated with limit (default 50) and offset. count is exact up to 100 and capped at 100 above that, so keep following next until it is null.

Example call:
curl -X GET "https://verification.didit.me/v3/transactions/{transaction_id}/related/?limit=50" \
-H "x-api-key: YOUR_API_KEY"

What to read from the response:
\- results[].uuid: use it with GET /v3/transactions/{transaction_id}/ for the full detail.
\- results[].txn_id, status, score, severity, amount, currency, txn_date: the summary of each related transaction.
\- results[].subject_vendor_data and counterparty_vendor_data: which party links it to this transaction.
\- next: URL of the next page, null on the last page.

Failure modes:
\- 400: limit or offset above 1000000.
\- 401: the API key has expired.
\- 403: missing or invalid API key ({"detail": "You do not have permission to perform this action."}), a scoped key without transactions: read, a key with workflow or status limits, or a request from outside the key's IP allowlist.
\- 404: no transaction with this uuid in my application ({"detail": "No Transaction matches the given query."}).
\- 429: more than 600 GET requests per minute with this key; wait Retry-After seconds and retry.

Side effects: none. This is a pure read.

For the full integration shape, see /integration/integration-prompt.`

\
Paste into Related transactions are linked through the `vendor_data` you send on each party when you [submit a transaction](/transaction-monitoring/transactions.md#subject-and-counterparty). Send the same `vendor_data` for the same person or company every time, and this endpoint returns their full history around any one transaction: the same list reviewers see under **Related transactions** on the [transaction detail](/transaction-monitoring/console.md#transaction-detail) in the Console.Each result has the same summary shape as [List transactions](/management-api/transactions/list.md). Call [Get transaction](/management-api/transactions/get.md) with a result's `uuid` for its parties, alerts and rule runs. ## OpenAPI ````yaml GET /v3/transactions/{transaction_id}/related/ openapi: 3.0.0 info: version: 3.0.0 title: Didit Verification API description: Identity verification API. Authenticate with x-api-key header. servers: - url: https://verification.didit.me security: [] tags: [] paths: /v3/transactions/{transaction_id}/related/: get: tags: - Transactions summary: List related transactions description: >- List the other transactions in your application that involve the same people or companies as this one. A transaction is related when any of its parties, in any role, has the same `vendor_data` as one of this transaction's parties. The transaction itself is never returned, and parties without `vendor_data` are ignored: when none of this transaction's parties has one, the result is always empty. Results use the summary shape of `GET /v3/transactions/`, newest first (`txn_date`, then `created_at`). Paginated with `limit` and `offset`; `count` is exact up to 100 and capped at 100 above that, so follow `next` until it is `null`. A scoped API key needs `transactions: read`; a key limited to some workflows or to approved sessions cannot call this endpoint. Send the same `vendor_data` for the same person or company on every [transaction](https://docs.didit.me/transaction-monitoring/transactions#subject-and-counterparty) to make this list complete. operationId: list_related_transactions parameters: - name: transaction_id in: path required: true description: >- Didit transaction UUID: the `uuid` returned by `POST /v3/transactions/` and `GET /v3/transactions/`. Your own `txn_id` is not accepted. schema: type: string format: uuid example: abcdef12-3456-7890-abcd-ef1234567890 - name: limit in: query required: false schema: type: integer default: 50 minimum: 1 maximum: 1000000 description: >- Number of transactions per page. Defaults to 50. A value that is not a positive integer falls back to 50; a value above 1000000 returns `400`. - name: offset in: query required: false schema: type: integer maximum: 1000000 minimum: 0 default: 0 description: >- Zero-based position of the first transaction to return. Prefer following `next`. A value that is not a whole number falls back to 0; a value above 1000000 returns `400`. responses: '200': description: A page of related transactions, newest first. content: application/json: schema: type: object required: - count - next - previous - results properties: count: type: integer description: >- Number of related transactions: exact up to 100, capped at 100 above that. Follow `next` instead of computing pages from it. next: type: string format: uri nullable: true description: Absolute URL of the next page, or `null` on the last page. previous: type: string format: uri nullable: true description: >- Absolute URL of the previous page, or `null` on the first page. results: type: array items: $ref: '#/components/schemas/TransactionSummary' examples: One related transaction: value: count: 1 next: null previous: null results: - uuid: abcdef99-3456-4890-abcd-ef1234567890 transaction_number: 4087 txn_id: your-txn-2026-10-02-017 transaction_type: finance action_type: deposit status: APPROVED source: LIVE direction: INBOUND amount: '250' currency: EUR currency_type: fiat preferred_currency_amount: '270.08' preferred_currency_code: USD payment_details: Card top-up txn_date: '2026-10-02T14:10:00Z' created_at: '2026-10-02T14:10:03.512244Z' score: 12 severity: LOW decision_reason_code: null decision_reason_label: null tags: [] subject_name: Maria Garcia subject_vendor_data: user-12345 subject_type: user subject_uuid: e1111111-2222-4333-8444-555555555555 counterparty_name: null counterparty_vendor_data: null counterparty_country: null subject_country: ESP assigned_to_name: null travel_rule_status: null application_id: aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee application_name: Production app organization_id: 11111111-2222-3333-4444-555555555555 organization_name: Example Org No party has vendor_data: value: count: 0 next: null previous: null results: [] '400': description: >- `limit` or `offset` is above 1000000. The body is a JSON array of messages, not an object. content: application/json: schema: type: array items: type: string examples: Limit too large: value: - limit must not exceed 1000000. Offset too large: value: - offset must not exceed 1000000. '401': description: >- The API key has expired. Only a key created with an expiry date can expire; after that date every request with it answers `401`. content: application/json: schema: type: object properties: detail: type: string examples: Expired key: value: detail: This API key has expired. '403': description: >- The request is not allowed. A missing or invalid API key gets the generic message (never `401`). content: application/json: schema: type: object properties: detail: type: string examples: Missing or invalid key: value: detail: You do not have permission to perform this action. Scoped key without transactions read: value: detail: This API key has no read access to transactions. Key limited to workflows or approved sessions: value: detail: >- This API key only reaches sessions inside its workflow or status limits, so it can't use this endpoint. Outside the key's IP list: value: detail: This API key can't be used from this IP address. '404': description: >- No transaction with this UUID exists in the application (never created, deleted, or owned by another application). A `transaction_id` that is not a UUID does not reach the API: it returns a `404` HTML page instead of this JSON body. content: application/json: schema: type: object properties: detail: type: string examples: Not found: value: detail: No Transaction matches the given query. '429': description: >- More than 600 GET requests per minute with this API key. Wait the number of seconds in `Retry-After`, then retry. content: application/json: schema: type: object properties: detail: type: string examples: Throttled: value: detail: >- GET request rate limit exceeded. You can make up to 600 requests per minute. headers: Retry-After: description: Seconds until the current one-minute window resets. schema: type: integer example: 23 X-RateLimit-Limit: description: Requests allowed per minute in this budget. schema: type: integer X-RateLimit-Remaining: description: Requests left in the current window. schema: type: integer X-RateLimit-Reset: description: Unix time when the window resets. schema: type: integer security: - ApiKeyAuth: [] x-codeSamples: - lang: curl label: curl source: >- curl -X GET 'https://verification.didit.me/v3/transactions/abcdef12-3456-7890-abcd-ef1234567890/related/?limit=50' \ -H 'x-api-key: YOUR_API_KEY' - lang: python label: Python source: |- import os import requests transaction_id = 'abcdef12-3456-7890-abcd-ef1234567890' resp = requests.get( f'https://verification.didit.me/v3/transactions/{transaction_id}/related/', headers={'x-api-key': os.environ['DIDIT_API_KEY']}, params={'limit': 50}, timeout=10, ) resp.raise_for_status() for tx in resp.json()['results']: print(tx['uuid'], tx['txn_date'], tx['status'], tx['amount'], tx['currency']) - lang: javascript label: JavaScript source: >- const transactionId = 'abcdef12-3456-7890-abcd-ef1234567890'; const resp = await fetch( `https://verification.didit.me/v3/transactions/${transactionId}/related/?limit=50`, { headers: { 'x-api-key': process.env.DIDIT_API_KEY } }, ); if (!resp.ok) throw new Error(`Related lookup failed: ${resp.status}`); const page = await resp.json(); for (const tx of page.results) console.log(tx.uuid, tx.status, tx.amount, tx.currency); components: schemas: TransactionSummary: type: object description: >- Summary of a monitored transaction, the shape `GET /v3/transactions/` lists. Call `GET /v3/transactions/{transaction_id}/` with `uuid` for parties, alerts and rule runs. properties: uuid: type: string format: uuid description: >- Didit transaction UUID. Use it as `{transaction_id}` on the transaction endpoints. transaction_number: type: integer nullable: true description: Application-scoped sequential number shown in the Console. txn_id: type: string nullable: true description: Your own identifier from the create call. Unique per application. transaction_type: type: string description: >- Category as stored: `finance`, `kyc`, `travelRule`, `userPlatformEvent`, `gamblingBet`, `gamblingLimitChange`, `gamblingBonusChange` or `auditTrailEvent`. action_type: type: string description: Sub-type within the category, for example `withdrawal`. status: type: string enum: - APPROVED - IN_REVIEW - DECLINED - AWAITING_USER description: Current monitoring verdict. source: type: string enum: - LIVE - IMPORTED description: >- `LIVE` for transactions submitted for monitoring, `IMPORTED` for historical imports. direction: type: string enum: - INBOUND - OUTBOUND description: Direction relative to the subject. amount: type: string description: >- Amount as a decimal string with trailing zeros removed (up to 18 decimal places). currency: type: string description: Currency code or crypto asset symbol of `amount`. currency_type: type: string nullable: true description: '`fiat` or `crypto` when known.' preferred_currency_amount: type: string nullable: true description: >- `amount` converted to the application's preferred currency, when a rate was available. preferred_currency_code: type: string nullable: true description: Currency of `preferred_currency_amount`. payment_details: type: string nullable: true description: Free-text payment reference. txn_date: type: string format: date-time description: When the transaction occurred. created_at: type: string format: date-time description: When Didit recorded it. score: type: integer description: Risk score. Higher is riskier. severity: type: string nullable: true enum: - UNKNOWN - LOW - MEDIUM - HIGH - CRITICAL - null description: Risk severity, `null` until something sets it. decision_reason_code: type: string nullable: true description: Machine-readable reason for the current `status`. decision_reason_label: type: string nullable: true description: Human-readable label for `decision_reason_code`. tags: type: array description: Tags on the transaction. items: type: object properties: uuid: type: string format: uuid name: type: string color: type: string description: Hex color, for example `#F59E0B`. description: type: string nullable: true source: type: string enum: - didit - custom description: Didit preset or custom tag. subject_name: type: string nullable: true description: Full name of the `APPLICANT` party. subject_vendor_data: type: string nullable: true description: Your `vendor_data` for the applicant. subject_type: type: string nullable: true enum: - user - business - null description: >- Whether the applicant is linked to a Didit user or business; `null` when it is linked to neither. subject_uuid: type: string format: uuid nullable: true description: UUID of the Didit user or business the applicant is linked to. subject_country: type: string nullable: true description: Country code of the applicant. counterparty_name: type: string nullable: true description: Full name of the `COUNTERPARTY` party, if any. counterparty_vendor_data: type: string nullable: true description: Your `vendor_data` for the counterparty. counterparty_country: type: string nullable: true description: Country code of the counterparty. assigned_to_name: type: string nullable: true description: Name of the Console reviewer assigned to the transaction. travel_rule_status: type: string nullable: true description: >- Status of the transaction's Travel Rule transfer, or `null` when it has none. application_id: type: string format: uuid description: Application that owns the transaction. application_name: type: string nullable: true description: Name of that application. organization_id: type: string format: uuid description: Organization that owns the application. organization_name: type: string nullable: true description: Name of that organization. securitySchemes: ApiKeyAuth: type: apiKey in: header name: x-api-key description: >- 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 missing, wrong, revoked or expired; 403 means 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. ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.