--- title: "Create bank account transactions" method: POST path: "/companies/{companyId}/connections/{connectionId}/push/bankAccounts/{accountId}/bankTransactions" tags: ["Bank account transactions"] --- # Create bank account transactions `POST /companies/{companyId}/connections/{connectionId}/push/bankAccounts/{accountId}/bankTransactions` ## Request - Base URL: `https://api.codat.io` - URL: `https://api.codat.io/companies/{companyId}/connections/{connectionId}/push/bankAccounts/{accountId}/bankTransactions` - Auth: API key in header `Authorization` The *Create bank account transactions* endpoint creates new [bank account transactions](https://docs.codat.io/accounting-api#/schemas/BankTransactions) for a given company's connection. [Bank account transactions](https://docs.codat.io/accounting-api#/schemas/BankTransactions) are records of money that has moved in and out of an SMB's bank account. **Integration-specific behavior** Required data may vary by integration. To see what data to post, first call [Get create bank transaction model](https://docs.codat.io/accounting-api#/operations/get-create-bankTransactions-model). ## Path parameters - `companyId` string, uuid, required: Unique identifier for your SMB in Codat. - `connectionId` string, uuid, required: Unique identifier for a company's data connection. - `accountId` string, required ## Query parameters - `timeoutInMinutes` integer - `allowSyncOnPushComplete` boolean ## Request body - CreateBankTransactions - `accountId` Schema (unresolved $ref) - `transactions` CreateBankAccountTransaction[] (unresolved $ref) ## Response `200` Success - CreateBankTransactionsResponse - `data` object - `accountId` Schema (unresolved $ref) - `transactions` CreateBankAccountTransaction[] (unresolved $ref) - `changes` PushOperationChange[], nullable: Contains a single entry that communicates which record has changed and the manner in which it changed. (unresolved $ref) - `dataType` 'accountTransactions' | 'balanceSheet' | 'bankAccounts' | 'bankTransactions' | 'billCreditNotes' | 'billPayments' | 'bills' | 'cashFlowStatement' | 'chartOfAccounts' | 'company' | 'creditNotes' | 'customers' | 'directCosts' | 'directIncomes' | 'invoices' | 'itemReceipts' | 'items' | 'journalEntries' | 'journals' | 'paymentMethods' | 'payments' | 'profitAndLoss' | 'purchaseOrders' | 'salesOrders' | 'suppliers' | 'taxRates' | 'trackingCategories' | 'transfers' | 'banking-accountBalances' | 'banking-accounts' | 'banking-transactionCategories' | 'banking-transactions' | 'commerce-companyInfo' | 'commerce-customers' | 'commerce-disputes' | 'commerce-locations' | 'commerce-orders' | 'commerce-paymentMethods' | 'commerce-payments' | 'commerce-productCategories' | 'commerce-products' | 'commerce-taxComponents' | 'commerce-transactions': Available data types - `companyId` Schema, required (unresolved $ref) - `pushOperationKey` string, uuid, required: A unique identifier generated by Codat to represent this single push operation. This identifier can be used to track the status of the push, and should be persisted. - `dataConnectionKey` Schema, required (unresolved $ref) - `requestedOnUtc` string, required: In Codat's data model, dates and times are represented using the ISO 8601 standard. Date and time fields are formatted as strings; for example: ``` 2020-10-08T22:40:50Z 2021-01-01T00:00:00 ``` When syncing data that contains `DateTime` fields from Codat, make sure you support the following cases when reading time information: - Coordinated Universal Time (UTC): `2021-11-15T06:00:00Z` - Unqualified local time: `2021-11-15T01:00:00` - UTC time offsets: `2021-11-15T01:00:00-05:00` > Time zones > > Not all dates from Codat will contain information about time zones. > Where it is not available from the underlying platform, Codat will return these as times local to the business whose data has been synced. - `completedOnUtc` string: In Codat's data model, dates and times are represented using the ISO 8601 standard. Date and time fields are formatted as strings; for example: ``` 2020-10-08T22:40:50Z 2021-01-01T00:00:00 ``` When syncing data that contains `DateTime` fields from Codat, make sure you support the following cases when reading time information: - Coordinated Universal Time (UTC): `2021-11-15T06:00:00Z` - Unqualified local time: `2021-11-15T01:00:00` - UTC time offsets: `2021-11-15T01:00:00-05:00` > Time zones > > Not all dates from Codat will contain information about time zones. > Where it is not available from the underlying platform, Codat will return these as times local to the business whose data has been synced. - `timeoutInMinutes` integer, nullable: Number of minutes the push operation must complete within before it times out. - `timeoutInSeconds` integer, nullable: Number of seconds the push operation must complete within before it times out. - `status` PushOperationStatus, required (unresolved $ref) - `errorMessage` string, nullable: A message about the error. - `validation` Validation (unresolved $ref) - `statusCode` integer, required: Push status code. ## Other responses - `400`: The request made is not valid. - `401`: Your API request was not properly authorized. - `402`: An account limit has been exceeded. The type of limit is described in the error property: - You have exceeded the 50-company limit that applies to a Free plan. Delete any companies you no longer need and retry the request. - The requested sync schedule is not allowed. You requested an hourly sync schedule but this functionality is not included in the Free plan. - Your Free account is older than 365 days and has expired. Contact support@codat.io. - `403`: You are using an outdated API key or a key not associated with that resource. - `404`: One or more of the resources you referenced could not be found. This might be because your company or data connection id is wrong, or was already deleted. - `429`: Too many requests were made in a given amount of time. Wait a short period and then try again. - `500`: There is a problem with our server. Please try again later. - `503`: The Codat API is temporarily offline for maintenance. Please try again later. ## Changes - **2024-02-13** `4bfab0afa6ca`: 8 info - added the optional property `validation` to the response with the `400` status - added the optional property `validation` to the response with the `401` status - added the optional property `validation` to the response with the `402` status - added the optional property `validation` to the response with the `403` status - …4 more - **2024-01-11** `3bc6baa03253`: 1 breaking, 2 warning, 1 info - the `allOf[subschema #1]/data` response's property type changed from `object` to no type for status `200` - removed the optional property `allOf[subschema #1]/data/accountId` from the response with the `200` status - removed the optional property `allOf[subschema #1]/data/transactions` from the response with the `200` status - added `#/components/schemas/CreateBankTransactions, subschema #2` to the `allOf[subschema #1]/data` response property `allOf` list for the response status `200` - **2023-12-15** `ba6ef154fd48`: 2 warning - added the new `itemReceipts` enum value to the `allOf[subschema #2: Push operation]/changes/items/recordRef/dataType` response property for the response status `200` - added the new `itemReceipts` enum value to the `allOf[subschema #2: Push operation]/dataType` response property for the response status `200` - …earlier changes not shown [Operation history](https://skmtc.dev/codatio/apis/accounting-api/changes/companies/:companyId/connections/:connectionId/push/bankAccounts/:accountId/bankTransactions/post.md) --- [API](https://skmtc.dev/codatio/apis/accounting-api.md) - [All operations](https://skmtc.dev/codatio/apis/accounting-api/llms.txt) - [OpenAPI document](https://skmtc.dev/codatio/apis/accounting-api/revisions/21d41189c461?raw)