Bank Connections

Push bank transactions for a customer_api account

Changed on

Batch upsert bank-feed transactions for a registered customer_api account identified by DualEntry financial account id.

Idempotency key is transaction external_trx_id (stored as source_id) scoped to the organization with customer_api as source_type. Each item must include account_id matching the registered customer account key. One bad item does not roll back other items; the response lists per-item outcomes.

Registration must be active (not unregistered). Max batch size is 250.

Side effects

  • If at least one transaction saves, DualEntry sets the connection last_sync_at, and sets successfully_aggregated_at when that is empty.
post/public/v2/bank-connections/accounts/{financial_account_id}/transactions/

Request

  • Base URL: https://api.dualentry.com
  • URL: https://api.dualentry.com/public/v2/bank-connections/accounts/{financial_account_id}/transactions/
  • Auth: none declared

Path parameters

financial_account_idinteger required

Headers

Idempotency-Keystring

Optional. A unique value (a UUID works well) identifying this operation. If the request is repeated with the same key, the original response is replayed instead of the operation running again, so a retry cannot create a duplicate record. Results are replayable for 48 hours. Reusing a key with a different request body returns 422.

Request body

Response

OK

successboolean required

Changes

  • 4b2d6ee0dff6Revision changes
    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

    • info

      added the optional property to the response with the status

  • f338ec8b3f52Revision changes
    • info

      endpoint added