Sign in
latestSwagger 2.02026-08-20196638916.1 KB

23d8982b533d

Data v2.Connector.Transactions
REGION.US
MULTI_TENANT

Delete Transactions

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.

post/data/v2/connector/transactions:batchDelete

Request body

externalOperationIdstring

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.

Example request

{
  "externalOperationId": "2677efa6cebe4d56bd30e0f239075dd8",
  "operationPriorityType": "BACKGROUND",
  "users": [
    {
      "accounts": [
        {
          "externalAccountId": "2345a0fa0026420b858283866b81196f",
          "transactions": [
            {
              "externalTransactionId": "618e29067ebd4faea47d733776e3e5b1"
            }
          ]
        }
      ],
      "externalUserId": "a480c0c82f684c268ab3c493c1222065"
    }
  ]
}

Response

A successful response.

externalOperationIdstring

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.

operationIdstring

Tink-generated data v2 Connector operation identifier. Obtained after operations initiated with data v2 Connector for Transactions endpoints.