--- title: "Ingest Transactions" method: POST path: "/data/v2/connector/transactions" tags: ["Data v2.Connector.Transactions", "REGION.US", "MULTI_TENANT"] --- # Ingest Transactions `POST /data/v2/connector/transactions` Initiates a transactions ingestion operation in the data v2 Connector. The request payload specifies the transactions to be ingested. This operation is asynchronous and upon initiation the API returns an `operationId` - a unique identifier for the ingestion 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 - TinkGoldenreceiverIngestOrUpdateTransactionsRequest — Request for transactions ingestion or update. - `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` TinkGoldenreceiverIngestOrUpdateTransactionsRequestUser[], required — The list of users for the data v2 Connector operation. - `accounts` TinkGoldenreceiverIngestOrUpdateTransactionsRequestAccount[], 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` TinkGoldenreceiverTransaction[], required — The list of account transactions for the data v2 Connector operation. - `amount` number, double, required — The transaction amount. Designed to capture the signed amount of the transaction in the account's main currency. For debit transactions, a negative sign (-) must be provided. For credit transactions, the amount should be provided as a positive value without any sign. - `bookedDateTime` string — For `BOOKED` transactions, intended to capture the date and time when the transaction was posted on the financial institution’s books. For `PENDING` transactions, it should indicate the expected booking date and time. The date and time should be specified as an ISO-8601 string in UTC (e.g., `2024-12-15T09:25:12.123Z`). At least one of the following `dateTime` fields must be provided: `bookedDateTime`, `valueDateTime`, or `transactionDateTime`. - `counterparties` TinkGoldenreceiverTransactionCounterparties — Available transaction counterparties. - `payee` TinkGoldenreceiverTransactionCounterpartiesCounterpartyInformation - `identifiers` TinkGoldenreceiverTransactionCounterpartiesCounterpartyInformationIdentifiers - … - `name` string — Intended to capture the name of the transaction counterparty from the financial institution. - `payer` TinkGoldenreceiverTransactionCounterpartiesCounterpartyInformation - `identifiers` TinkGoldenreceiverTransactionCounterpartiesCounterpartyInformationIdentifiers - … - `name` string — Intended to capture the name of the transaction counterparty from the financial institution. - `descriptions` TinkGoldenreceiverTransactionDescriptions, required - `detailed` TinkGoldenreceiverTransactionTransactionInformation - `unstructured` string — Unstructured transaction detailed description. Intended to capture a detailed narrative and unstructured text message containing relevant details of transactions, such as remittance information or purpose. - `original` string, required — Transaction original description. Designed to capture the transaction descriptions as displayed to the user in the transaction history list. - `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. - `merchantInformation` TinkGoldenreceiverTransactionMerchantInformation - `merchantCategoryCode` string — Intended to capture the merchant category code (MCC) for the purchase transaction. Provided value must be a four-digit number. - `merchantLocation` TinkGoldenreceiverTransactionMerchantInformationMerchantLocation - `address` TinkGoldenreceiverTransactionMerchantInformationMerchantLocationAddress - … - `geoLocation` TinkGoldenreceiverTransactionMerchantInformationMerchantLocationGeoLocation - … - `merchantName` string — Intended to capture the merchant name for the transaction, specifically the merchant of record for purchases. - `merchantNationalId` string — Intended to capture government-issued company identifier used to recognise and track a merchant's legal entity. - `metadata` TinkGoldenreceiverTransactionMetadata - `custom` object — Intended to capture custom metadata. This feature is disabled by default. Please contact support to learn how to configure custom metadata for your app. - `tags` string — To capture the capture user-provided or institution-provided tags for transaction. The string should consist of one or multiple substrings, each starting with # followed by letters and numbers (example: "#tag1 #tag2 #tag3"). Note: available only for Money Manager product. - `reference` string — Intended to capture the financial institution reference of the transaction. - `status` 'BOOKED' | 'PENDING' — Status of the transaction. - BOOKED: The transaction is booked at the financial institution. - PENDING: The transaction is pending at the financial institution. - `transactionDateTime` string — Intended to capture the date and time when the transaction event was first initiated. For example, when a payment card was authorised at the point of sale (before it was booked) or when a money transfer was first initiated (before it was executed). The date and time should be specified as an ISO-8601 string in UTC (e.g., `2024-12-15T09:25:12.123Z`). At least one of the following `dateTime` fields must be provided: `bookedDateTime`, `valueDateTime`, or `transactionDateTime`. - `types` TinkGoldenreceiverTransactionTypes - `financialInstitutionTypeCode` string — Intended to capture the financial institution’s own classification of the transaction type. - `transactionTypeCode` 'UNDEFINED' | 'CREDIT_CARD' | 'PAYMENT' | 'WITHDRAWAL' | 'DEFAULT' | 'TRANSFER' — - UNDEFINED: Type undefined. - CREDIT_CARD: Credit card. - PAYMENT: Payment. - WITHDRAWAL: Withdrawal. - DEFAULT: Default. - TRANSFER: Transfer. - `valueDateTime` string — Intended to capture the date and time when assets either become available or cease to be available to the account owner. The date and time should be specified as an ISO-8601 string in UTC (e.g., `2024-12-15T09:25:12.123Z`). At least one of the following `dateTime` fields must be provided: `bookedDateTime`, `valueDateTime`, or `transactionDateTime`. - `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` — Ingest 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)