---
title: "Delete Transactions"
method: POST
path: "/data/v2/connector/transactions:batchDelete"
tags: ["Data v2.Connector.Transactions", "REGION.US", "MULTI_TENANT"]
---

# Delete Transactions

`POST /data/v2/connector/transactions:batchDelete`

Initiates a transactions deletion operation in the data v2 Connector.

The request payload specifies the transactions to be deleted.

This operation is asynchronous and upon initiation the API returns an `operationId` - a unique identifier for the deletion process.

The `operationId` can be used to retrieve and track the status of the operation. Refer to the documentation for the relevant Tink product you use with the data v2 Connector to learn how to work with `operationId` in your specific product context.

## Request body

- TinkGoldenreceiverDeleteTransactionsRequest — Request for transactions deletion.
  - `externalOperationId` string — When provided, serve as the unique identifier of the operation generated and provided by the customer. Allows for the reconciliation of externally initiated operations with Tink-generated identifiers for the same operation. The identifier must be unique and can include alphanumeric characters, hyphens, braces, and padding characters. It must follow recognised GUID/UUID formats, either with or without braces, and can also be Base64url encoded, with or without padding.
  - `operationPriorityType` 'REAL_TIME' | 'BACKGROUND' — Defines the priority of the data v2 Connector operation. - REAL_TIME: For real-time scenarios where immediate feedback is required, such as processing recently made transactions or providing quick user feedback during onboarding by processing the most recent transactions first. Not intended for large-scale transaction history backfilling. - BACKGROUND: For non-time-critical scenarios or when the operation consists of a large number of transactions, e.g., when backfilling user transaction data. Serves as a fallback to ensure API performance or when operation priority type is not provided by the customer.
  - `users` TinkGoldenreceiverDeleteTransactionsRequestUser[], required — The list of users for the data v2 Connector operation. Currently, only one user is allowed per operation.
    - `accounts` TinkGoldenreceiverDeleteTransactionsRequestAccount[], required — The list of accounts for the data v2 Connector operation.
      - `externalAccountId` string, required — The external account Id specified by customer when ingesting Account.
      - `transactions` TinkGoldenreceiverDeleteTransactionsRequestTransaction[], required — The list of account transactions for the data v2 Connector operation.
        - `externalTransactionId` string, required — The unique identifier of transaction provided by customer. The identifier must be unique and can include alphanumeric characters, hyphens, braces, and padding characters. It must follow recognised GUID/UUID formats, either with or without braces, and can also be Base64url encoded, with or without padding.
    - `externalUserId` string, required — The external user Id specified by customer when creating User.

## Response `200`

A successful response.

- TinkGoldenreceiverOperationResponse
  - `externalOperationId` string — This is the `externalOperationId` included in the request to the data v2 Connector, if provided. It enables correlation between the client’s own operation tracking and the corresponding asynchronous operation initiated in the data v2 Connector.
  - `operationId` string — Tink-generated data v2 Connector operation identifier. Obtained after operations initiated with data v2 Connector for Transactions endpoints.

## Other responses

- `202` — Delete request accepted
- `400` — The request does not pass validation. Check the error message or the documentation of each field for more information.
- `401` — Authorization token is missing, or not valid
- `403` — You are not allowed to access the requested resource
- `default` — An unexpected error response.

---

[API](https://skmtc.net/tink/apis/tink-api.md) · [All operations](https://skmtc.net/tink/apis/tink-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/tink/tink-api/revisions/23d8982b533d/schema)