--- title: "Get Transactions From Batch Payments Templates" method: GET path: "/transactions/batchable" tags: ["Transactions"] --- # Get Transactions From Batch Payments Templates `GET /transactions/batchable` Get all transactions that have the potential to be included in a batch payment. ## Query parameters - `enabled` boolean - `page_token` string — Optional pagination token to be provided to retrieve subsequent pages, returned from previous get - `limit` integer — Maximum number of objects to return per page. If the limit is greater than 100, then it will be set to 100. ## Response `200` The posted transactions that are able to be included in a batch payment. - PostedTransactions - `next_page_token` string, nullable, required — If returned, use the next_page_token to query for the next page of results. Not returned if there are no more rows. - `result` PostedTransaction[], required — List of posted transactions - `created` string, date-time, required — The creation date of the transaction - `data` PostedTransactionData, required - `external_data` ExternalData, nullable — an unstructured json blob representing additional transaction information supplied by the integrator. - `force_post` boolean, required — Whether or not the hold was forced (spending controls ignored) - `hold_id` string, uuid — The uuid of the hold (pending transaction) that this transaction originated from, if any. - `lines` TransactionLine1[], required — The set of accounting entries associated with this transaction. For example, a debit to a customer account will have a corresponding credit in a general ledger account. - `account_id` string, required — The account uuid associated with this transaction line - `account_no` string, required — The account number associated with this transaction line - `amount` integer, required — The amount (in cents) of the transaction - `avail_balance` integer, required — The account "available balance" at the point in time this (to be deprecated) transaction was posted - `available_balance` integer, required — The account "available balance" at the point in time this transaction was posted - `balance` integer, required — The account balance at the point in time this transaction was posted - `created` string, date-time, required — The creation date of the transaction - `currency` string, required — ISO 4217 alphabetic currency code of the transfer amount - `dc_sign` 'credit' | 'debit', required — The `dc_sign` represents the direction money was moved. - `is_fee` boolean, required — Whether or not this line is considered a fee - `is_gl_acc` boolean, required — Whether or not this line represents a GL account - `is_offset` boolean, required — Whether or not this line is considered the "offset" line - `is_primary` boolean, required — Whether or not this line is considered the "primary" line - `meta` object, nullable, required - `network` string, required — The network this transaction is associated with - `related_line` integer, required - `seq` integer, required - `sweep_agg_id` string, uuid — The sweep aggregation that this line is mapped to. - `tenant` string, required — The id of the tenant containing the resource. This is relevant for Fintechs that have multiple workspaces. - `updated` string, date-time, required — The date the transaction was last updated - `uuid` string, uuid, required - `memo` string, required — A short note to the recipient - `metadata` object, nullable, required - `original_trx` string, uuid — The "original" transaction that this transaction is related to. This is only populated in the case of reversed transactions. - `parent_trx` string, uuid — The "parent" transaction that this transaction is related to. This is only populated in the case of scheduled transactions. - `risk_info` RiskInfo, nullable — Information received by the transaction risk/fraud service related to this transaction - `user_data` UserData, nullable — An unstructured JSON blob representing additional transaction information specific to each payment rail. - `vendor_info` TransactionVendorInfo — Vendor information for external transactions - `vendor_data` TransactionVendorData, required — Vendor-specific data - `loanpro` TransactionLoanproVendorData - `bucket_id` integer — LoanPro bucket ID - `loc_id` integer — LoanPro line of credit account ID - `swipe_id` string, uuid — LoanPro Secure Payments swipe UUID - `transaction_id` integer — LoanPro LMS transaction ID - `transaction_type` 'CHARGE' | 'CREDIT' | 'FINANCE_CHARGE' | 'PAYMENT' | 'SWIPE' — The LoanPro transaction type this maps to - `vendor_type` 'LOANPRO', required — The type of vendor associated with this transaction - `disputes` TransactionDispute[] — The set of disputes related to this transaction. Since a dispute can be for a partial amount of a transaction, a single transaction can be involved in multiple disputes. - `created` string, date-time, required — The creation time of the dispute - `external_case_reference` string — The external case number or id for the dispute (eg: from a vendor such as Marqeta), if one exists. - `id` string, uuid, required — The unique identifier of the dispute. - `internal_case_reference` string — The internal case number or id for the dispute in the Synctera platform, if one exists. - `status` 'ARBITRATION' | 'CASE_LOST' | 'CASE_OPEN' | 'CASE_WON' | 'CHARGEBACK_INITIATED' | 'NETWORK_REJECTED' | 'PREARBITRATION' | 'REPRESENTMENT', required - `updated` string, date-time, required — The time the dispute was last updated - `effective_date` string, date-time, required — The "effective date" of a transaction. This may be earlier than posted_date in some cases (for example, a transaction that occurs on a Saturday may not be posted until the following Monday, but would have an effective date of Saturday) - `enhanced_transaction` EnhancedTransactionResponse — Financial data that has been refined by cleansing, categorizing and adding metadata. For example, inconsistencies in raw transaction data that were introduced via data aggregation are removed, transactions are categorized into groups such as "groceries" or utilities", and metadata (such as merchant names or location and timing details) are added for clarity. - `id` integer, required - `idemkey` string, required — The idempotency key used when initially creating this transaction. - `info_only` boolean, required — Whether or not this transaction represents a purely informational operation or an actual money movement - `lead_mode` boolean, required — Whether or not this transaction was created operating in "lead ledger" mode - `posted_date` string, date-time, required — The date the transaction was posted. This is the date any money is considered to be added or removed from an account. - `reference_id` string, nullable, required — An external ID provided by the payment network to represent this transaction. This will always be null for internal transfers. - `settlement_date` string, date — The date the transaction was settled according to Synctera's platform. Generally, this can be interpretted the date the transaction was actually processed and settlement by the payment network. - `status` string, required - `subtype` string, required — The specific transaction type. For example, for `ach`, this may be "outgoing_debit". - `tenant` string, required — The id of the tenant containing the resource. This is relevant for Fintechs that have multiple workspaces. - `transaction_time` string, date-time, required — The time the transaction occurred. - `type` string, required — The general type of transaction. For example, "card" or "ach". - `updated` string, date-time, required — The date the transaction was last updated - `uuid` string, uuid, required — The unique identifier of the transaction. ## Other responses - `400` — BadRequest - `401` — Unauthorized - `500` — Internal server error --- [API](https://skmtc.net/synctera/apis/synctera-api.md) · [All operations](https://skmtc.net/synctera/apis/synctera-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/synctera/synctera-api/revisions/b0d812e6cdd0/schema)