Sintropix Bank Accounts API: Manage Accounts and Feeds

A Bank Account is a real-world account an Entity holds at a financial institution, such as a checking account or a credit card. Each account is scoped to a single Entity, denominated in one currency, and mapped to exactly one Ledger Account where its booked activity accumulates. This page covers the endpoints for managing Bank Accounts and their optional bank data feeds.

Open in the app. This resource has a page in the Sintropix web app at https://app.sintropix.com/{entityId}/banks/{bankAccountId}, where each id in braces is the same UUID as in the API route or response. That page is the reconciliation view for the account. Account settings are at /{entityId}/settings/bank-accounts, and ?open={bankAccountId} there opens the account's edit. When you mention a record to a user, include that link. See Link to the App for the full URL grammar.

Base path

All Bank Account routes are prefixed under:

/api/entities/:entityId/bank-accounts

Feed sub-routes live under:

/api/entities/:entityId/bank-accounts/:bankAccountId/feed

Path parameters :entityId and :bankAccountId are UUIDs. To start a feed, connect a bank Provider as an Integration, then map one of its discovered accounts to a Bank Account. See Bank Feeds.

Authentication

Use a session cookie or pass x-api-key: $SINTROPIX_API_KEY. Mutations with an API key also require x-audit-actor: my-agent. See Get an API Key.

Bank Account kinds

A Bank Account has one of two kinds, validated at creation against the mapped Ledger Account’s type:

Kind	Mapped Ledger Account type
`bank`	Asset, with the Cash sub-type
`card`	Liability

List bank accounts

GET /api/entities/:entityId/bank-accounts

Returns every Bank Account for the Entity with a computed summary. The response is a bare JSON array; each element has the fields below.

Response schema

Each Bank Account in the list carries:

Field	Type	Description
`id`	UUID	Account identifier
`entityId`	UUID	Owning Entity
`name`	string	Display name
`kind`	`bank` \| `card`	Account kind
`ledgerAccountId`	UUID	Mapped Ledger Account
`currency`	string	ISO 4217 currency code
`accountNumber`	string \| null	The number the bank knows the account by. `null` when not set. To be the Cuenta de cargo of a Payment Batch’s BCI bank file, an account in `CLP` needs it.
`bankCode`	string \| null	The bank that holds the account, as its CMF code from `GET /banks`, for example `016` for BCI. `null` when not set. The app draws the account’s logo from it, and only an account with `bankCode` `016` can be the Cuenta de cargo of a BCI bank file.
`feed`	object \| null	Active feed, if any (see below)
`createdAt`	ISO datetime	Creation timestamp
`updatedAt`	ISO datetime	Last update timestamp
`balance`	integer	Signed balance in minor units
`unreconciledCount`	integer	Movements still to reconcile: those with no booking entry, and those booked with part still on the Suspense Account. Excluded Movements don’t count

The last two fields (balance and unreconciledCount) are the summary; endpoints that return a Bank Account without summary omit them. The feed object, when present, contains:

Field	Type	Description
`integrationId`	UUID	The Integration that feeds the account
`integrationKind`	`fintoc` \| `plaid` \| `global66` \| `cardda` \| `dlocal` \| `mercadopago` \| `polar` \| `stripe`	The kind of that Integration
`providerAccountId`	string	Provider-side account handle
`institutionName`	string \| null	The bank’s display name for a `fintoc` or `plaid` feed; `null` for every other kind
`lastSyncedAt`	ISO datetime \| null	Last sync that landed, whether or not it tied out. `null` until the first sync lands
`tieOut`	object \| null	The tie-out verdict of the last sync that judged the feed. `null` until the first sync judges it

[
  {
    "id": "0190e000-0000-7000-8000-000000000001",
    "entityId": "0190a000-0000-7000-8000-000000000001",
    "name": "Primary Checking",
    "kind": "bank",
    "ledgerAccountId": "0190d000-0000-7000-8000-000000000001",
    "currency": "CLP",
    "accountNumber": "12345678",
    "bankCode": "001",
    "feed": {
      "integrationId": "0192a8b4-0000-7000-8000-000000000001",
      "integrationKind": "fintoc",
      "providerAccountId": "acc_123",
      "institutionName": "Banco de Chile",
      "lastSyncedAt": "2026-02-01T12:00:00.000Z",
      "tieOut": {
        "status": "tied_out",
        "reportedBalance": 1250000,
        "since": "2026-01-15T09:30:00.000Z"
      }
    },
    "createdAt": "2026-01-15T09:30:00.000Z",
    "updatedAt": "2026-02-01T12:00:00.000Z",
    "balance": 1250000,
    "unreconciledCount": 3
  }
]

Example

curl -s https://api.sintropix.com/api/entities/$ENTITY_ID/bank-accounts \
  -H "x-api-key: $SINTROPIX_API_KEY"

Create a bank account

POST /api/entities/:entityId/bank-accounts

Creates a new Bank Account.

Body parameters

Field	Type	Required	Description
`id`	UUID	Yes	Client-supplied identifier for idempotency
`name`	string	Yes	Display name (non-empty)
`kind`	`bank` \| `card`	Yes	Account kind
`ledgerAccountId`	UUID	Yes	Ledger Account to map; type must match kind
`currency`	string	Yes	ISO 4217 currency code
`accountNumber`	string \| null	No	The number the bank knows the account by. Trimmed; a blank value is refused. Omit or send `null` to leave it unset.
`bankCode`	string \| null	No	CMF code of the bank that holds the account, from `GET /banks`. An unknown code is refused with `400` and `BANK_ACCOUNT_BANK_UNKNOWN_ERROR`. Omit or send `null` to leave it unset.

Response

Returns 201 Created with the created Bank Account, including the balance and unreconciledCount summary fields, in the same shape as the list response.

Status codes

Status	Meaning
201	Created
400	Validation error, an unknown `currency` (`UNKNOWN_CURRENCY_ERROR`), or an unknown `bankCode` (`BANK_ACCOUNT_BANK_UNKNOWN_ERROR`, with `params.bankCode`)
404	Entity or Ledger Account not found
409	`id` already exists (`BANK_ACCOUNT_ID_CONFLICT_ERROR`)
409	The Ledger Account’s type doesn’t match `kind` (`BANK_ACCOUNT_KIND_LEDGER_ACCOUNT_TYPE_MISMATCH_ERROR`)
409	A `bank` account maps to a Ledger Account that isn’t a Cash Account (`BANK_ACCOUNT_LEDGER_ACCOUNT_NOT_CASH_ERROR`)
409	The Ledger Account is the reserved suspense account (`LEDGER_ACCOUNT_SUSPENSE_RESERVED_ERROR`)

Example

curl -s https://api.sintropix.com/api/entities/$ENTITY_ID/bank-accounts \
  -X POST \
  -H "Content-Type: application/json" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -d '{
    "id": "0190e000-0000-7000-8000-000000000001",
    "name": "Primary Checking",
    "kind": "bank",
    "ledgerAccountId": "0190d000-0000-7000-8000-000000000001",
    "currency": "CLP",
    "bankCode": "016"
  }'

Update a bank account

PATCH /api/entities/:entityId/bank-accounts/:bankAccountId

Updates the name, the account number, and the bank of an existing Bank Account. Only name, accountNumber, and bankCode are editable through this endpoint.

Body parameters

Field	Type	Required	Description
`name`	string	Yes	New display name (non-empty)
`accountNumber`	string \| null	No	The number the bank knows the account by. Trimmed; a blank value is refused. `null` clears it. Omit to keep the current number.
`bankCode`	string \| null	No	CMF code of the bank that holds the account, from `GET /banks`. An unknown code is refused with `400` and `BANK_ACCOUNT_BANK_UNKNOWN_ERROR`. `null` clears it and keeps the account number. Omit to keep the current bank.

Response

Returns 200 OK with the updated Bank Account, in the same shape as the list response minus balance and unreconciledCount.

Status codes

Status	Meaning
200	Updated
400	Validation error, or an unknown `bankCode` (`BANK_ACCOUNT_BANK_UNKNOWN_ERROR`)
404	Bank Account not found

Example

curl -s https://api.sintropix.com/api/entities/$ENTITY_ID/bank-accounts/$BANK_ACCOUNT_ID \
  -X PATCH \
  -H "Content-Type: application/json" \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -d '{"name": "Updated Checking Name"}'

Delete a bank account

DELETE /api/entities/:entityId/bank-accounts/:bankAccountId

Removes a Bank Account. Deletion is allowed only when the account has no Movements and no active feed.

Response

Returns 200 OK with:

Field	Type	Description
`deletedBankAccountId`	UUID	The removed account’s identifier

Status codes

Status	Meaning
200	Deleted
404	Bank Account not found
409	Account has Movements (`BANK_ACCOUNT_HAS_MOVEMENTS_ERROR`) or an active feed (`BANK_ACCOUNT_FED_ERROR`)

Example

curl -s https://api.sintropix.com/api/entities/$ENTITY_ID/bank-accounts/$BANK_ACCOUNT_ID \
  -X DELETE \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent"

Delete a bank account feed

DELETE /api/entities/:entityId/bank-accounts/:bankAccountId/feed

Removes the active bank data feed from a Bank Account. The account and its existing Movements remain; no new feed data will be ingested.

Response

Returns 200 OK with the Bank Account, in the same shape as the list response minus balance and unreconciledCount; feed is now null.

Status codes

Status	Meaning
200	Feed removed
404	Bank Account not found or not fed

Example

curl -s https://api.sintropix.com/api/entities/$ENTITY_ID/bank-accounts/$BANK_ACCOUNT_ID/feed \
  -X DELETE \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent"

Sync a bank account feed

POST /api/entities/:entityId/bank-accounts/:bankAccountId/feed/sync

Triggers a manual sync of the Bank Account’s feed. The server reads the latest window from the Provider, lands new Movements, and records the outcome. Sintropix also syncs every feed on its own every four hours, with the same rules. A sync lands its Movements even when they don’t add up to the balance the Provider reports. It then flags the feed as out of tie-out. See Tie-out. The only sync that lands nothing is one that finds a restatement it can’t take by itself. A sync also updates the Movements it already landed when the Provider changed them since, whether they’re unbooked, booked, or reconciled:

The description becomes the Provider’s newest text for the Movement. Some banks complete a movement’s text a day after it posts, so the description fills in with the counterparty on the next sync.
The Additional Information lines the Provider writes are rewritten. Lines you added stay, in their order.
The Partner is set from the counterparty’s tax ID, such as a RUT, only when the Movement has none.

A sync never changes a landed Movement’s amount, side, or date, and never touches the Ledger Entry that books it, so the entry’s memo stays as you wrote it. A changed description isn’t a restatement. Each Movement it updates counts in updatedCount.

Response

Returns 201 Created with:

Field	Type	Description
`landedCount`	integer	New Movements written (nonnegative)
`skippedCount`	integer	Movements already present (nonnegative)
`updatedCount`	integer	Of the `skippedCount` Movements, those Sintropix updated because the Provider changed their details since they landed, such as the description (nonnegative)

Status codes

Status	Meaning
201	Sync completed, whether or not it tied out. Read `feed.tieOut` on the Bank Account for the verdict
404	Bank Account not found or not fed
409	The Provider restated a Movement the feed already landed, and a person must accept the Provider’s version (`BANK_FEED_SYNC_RESTATEMENT_ERROR`). Nothing landed. See Restatement
409	The sync found a restatement, but another sync landed after it read the Provider (`BANK_FEED_SYNC_RACED_ERROR`). Nothing landed. Sync again
424	The Provider refused the read or the landing (`BANK_FEED_PROVIDER_FAILURE_ERROR` and the other codes in Provider refusals)
503	The Provider can’t be reached right now (`BANK_FEED_PROVIDER_UNREACHABLE_ERROR`). Retry later

Example

curl -s https://api.sintropix.com/api/entities/$ENTITY_ID/bank-accounts/$BANK_ACCOUNT_ID/feed/sync \
  -X POST \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent"

Tie-out

Each sync checks that the Bank Account’s Movements add up to the balance the Provider reports. The feed keeps the verdict of the last sync that judged it, and every read of the Bank Account serves it as feed.tieOut:

Field	Type	Description
`status`	`tied_out` \| `out_of_tie_out` \| `restated`	The verdict (see below)
`reportedBalance`	integer	The balance the Provider reported, in minor units, that the sync checked against
`since`	ISO datetime	When the feed entered this status. A later sync with the same verdict keeps it

The other side of the check is the Bank Account’s balance, the sum of its Movements. The difference is reportedBalance minus balance.

`status`	Meaning
`tied_out`	The Movements add up to the reported balance.
`out_of_tie_out`	The sync landed its Movements, but they don’t add up to the reported balance. It’s usually a movement the bank already counts and hasn’t served yet. The next sync that lands it ties out again, with a new `since`.
`restated`	The sync found a restatement that a person must accept, and landed nothing.

Nothing blocks on out_of_tie_out: Movements keep landing, and you can book and reconcile them as usual. Use since to tell a short lag from a lasting difference. Most differences clear on their own within two days. If one lasts longer, contact Sintropix support. In the app, the movement queue of the Bank Account shows the verdict on every load, whether you or the scheduled sync ran it. An account out of tie-out shows No cuadra con el banco desde …, with the balance the bank reports, the sum of the Movements, and the difference.

{
  "integrationId": "0192a8b4-0000-7000-8000-000000000001",
  "integrationKind": "fintoc",
  "providerAccountId": "acc_123",
  "institutionName": "Banco de Chile",
  "lastSyncedAt": "2026-10-16T12:00:00.000Z",
  "tieOut": {
    "status": "out_of_tie_out",
    "reportedBalance": 1415979,
    "since": "2026-10-15T20:00:00.000Z"
  }
}

Restatement

A restatement is a Movement the feed already landed that the Provider no longer serves: it dropped it, or serves it again under another reference. Only Movements dated inside the window the Provider still serves count, from the feed start date on. A Provider whose history simply stops reaching its oldest days isn’t restating anything. Landing that window as it is would write the Movement twice. Instead, the restated Movements give way to the Provider’s version: Sintropix deletes them and lands what the Provider serves now. That happens in one of two ways. The sync takes it by itself when both of these hold:

No restated Movement is booked or excluded.
Each restated day still adds up: the restated Movements of the day sum to what the Provider now serves for that day that the feed hasn’t landed.

The sync then replaces the restated Movements and lands the window as usual, with no 409. Otherwise, a person accepts it. The sync lands nothing, sets feed.tieOut.status to restated, and answers 409:

{
  "code": "BANK_FEED_SYNC_RESTATEMENT_ERROR",
  "params": { "restatedExternalRefs": ["mov_ZxENnDHv6xPkDeJk"] }
}

restatedExternalRefs lists the Provider references of the landed Movements the Provider no longer serves. Every later sync is refused the same way until someone accepts the Provider’s version. The first refused sync also opens a Task in the Organization’s Tareas that names the Bank Account. To accept it in the app:

Open the Bank Account. Its movement queue shows Sincronización detenida desde ….
Click Revisar cambios del banco. The dialog lists each restated day, with the Movements in the books (En los libros) beside what the bank lists now (El banco informa ahora), and the total of each side.
If a restated Movement is marked Contabilizado or Excluido, unbook it or include it again first.
Click Aceptar la versión del banco.

Accepting takes the Provider’s version whatever each day adds up to. It refuses while a restated Movement is booked or excluded, because replacing it would undo a person’s decision. The ERP Thread and files of a replaced Movement are deleted with it.

GET `/feed/restatement`

GET /api/entities/:entityId/bank-accounts/:bankAccountId/feed/restatement

Read the restatement day by day. Sintropix reads it live from the Provider each time and stores nothing. days is empty when the Provider restates nothing.

Field	Type	Description
`days`	array	One item per restated day. See below
`fingerprint`	string	Names the rows this review shows. Send it back to accept this exact version

Each item of days:

Field	Type	Description
`date`	date (`YYYY-MM-DD`)	The day
`landedMovements`	array	The restated Movements of the day: `{ id, movementDate, amount, side, description, externalRef, ledgerEntryId, excludedAt }`. A `ledgerEntryId` means the Movement is booked, and an `excludedAt` that it’s excluded
`servedMovements`	array	What the Provider serves for the day that the feed hasn’t landed: `{ providerMovementId, amount, description }`, with a signed `amount` in minor units, a debit positive
`landedNet`	integer	The sum of `landedMovements`, signed, in minor units
`servedNet`	integer	The sum of `servedMovements`, signed, in minor units. It differs from `landedNet` when the Provider changed what the day adds up to

POST `/feed/restatement/acceptance`

POST /api/entities/:entityId/bank-accounts/:bankAccountId/feed/restatement/acceptance

Accept the Provider’s version of the restatement you reviewed. Sintropix deletes the restated Movements and lands the window, as a sync does. It needs the books write permission, so a viewer can’t accept.

Field	Type	Required	Description
`fingerprint`	string	Yes	The `fingerprint` of the review you read with `GET /feed/restatement`

Returns 201 Created with the sync result: landedCount, skippedCount, and updatedCount. The feed’s tie-out is judged again, as on any sync.

Status	Meaning
201	Accepted. The window landed
404	Bank Account not found or not fed
409	A restated Movement is booked or excluded (`BANK_FEED_RESTATEMENT_HELD_ERROR`). `params.bankMovementIds` names them. Unbook or include them, then accept again
409	The Provider’s version changed since you read it, or another sync landed meanwhile (`BANK_FEED_SYNC_RACED_ERROR`). Read the restatement again and review it
424	The Provider refused the read (see Provider refusals)

curl -s https://api.sintropix.com/api/entities/$ENTITY_ID/bank-accounts/$BANK_ACCOUNT_ID/feed/restatement/acceptance \
  -X POST \
  -H "x-api-key: $SINTROPIX_API_KEY" \
  -H "x-audit-actor: my-agent" \
  -H "x-audit-reason: Accept the bank's rewrite of 19 September" \
  -H "Content-Type: application/json" \
  -d '{"fingerprint": "'"$FINGERPRINT"'"}'

Rate limits

Bank Account endpoints share the global rate limit of 25,000 requests per hour per API key.

​Base path

​Authentication

​Bank Account kinds

​List bank accounts

​Response schema

​Example

​Create a bank account

​Body parameters

​Response

​Status codes

​Example

​Update a bank account

​Body parameters

​Response

​Status codes

​Example

​Delete a bank account

​Response

​Status codes

​Example

​Delete a bank account feed

​Response

​Status codes

​Example

​Sync a bank account feed

​Response

​Status codes

​Example

​Tie-out

​Restatement

​GET /feed/restatement

​POST /feed/restatement/acceptance

​Rate limits

Base path

Authentication

Bank Account kinds

List bank accounts

Response schema

Example

Create a bank account

Body parameters

Response

Status codes

Example

Update a bank account

Body parameters

Response

Status codes

Example

Delete a bank account

Response

Status codes

Example

Delete a bank account feed

Response

Status codes

Example

Sync a bank account feed

Response

Status codes

Example

Tie-out

Restatement

GET `/feed/restatement`

POST `/feed/restatement/acceptance`

Rate limits