Push bank accounts, transactions, and balances into a bank feed

POST/api/v1/credit/bank-feeds/{bank_feed_id}/ingest

For partners that pull merchant bank data in their own backend and push it directly into DayZero without BigQuery (provider: direct_push, or to seed a feed immediately). Each cash account gets a bank ledger on the merchant's DayZero business, posted transactions are booked with journal entries, voided transactions are hidden, and daily balance snapshots are interpolated across the history so underwriting and bank-settlement payment matching read them immediately. Idempotent on transaction_id and (account_id, as_of).

Operation ID: ingest_credit_bank_feed·View as markdown·OpenAPI slice

Authentication

Bearer token authentication. Pass your DayZero API token in the Authorization header and the target business UUID in x-business-id.

Parameters

Path

bank_feed_idstringrequired: The bank feed to push bank data into.

Request body

Schema: BankFeedIngestRequest

accountsarray · BankFeedIngestAccountBankFeedIngestAccount

Bank accounts on the merchant's feed.

6 fields

account_idstringrequired

Your stable id for the bank account (e.g. fca_... or acct_...).

institution_namestring

The bank's name.

display_namestring

The account's display name.

last4string

The last four digits of the account.

statusstring

Account status (active, inactive).

typestring

Account kind (cash is synced to a bank ledger; credit is skipped).

One of: cash, credit

transactionsarray · BankFeedIngestTransactionBankFeedIngestTransaction

Bank transactions to upsert or void.

9 fields

transaction_idstringrequired

Your idempotency key for the bank transaction.

account_idstringrequired

The account_id this transaction belongs to.

amount_centsintegerrequired

Signed amount in cents (cash-flow sign: money into the account is positive, money leaving the account is negative).

currencystring

Three-letter ISO currency code.

descriptionstringrequired

The bank statement description.

statusstring

posted books onto the merchant's ledger; pending is skipped; void removes a previously posted transaction.

One of: posted, pending, void

transacted_onstring · daterequired

The calendar date the transaction posted at the bank.

categorystring

The transaction's category as a Plaid personal-finance detailed code, e.g. BANK_FEES_OVERDRAFT_FEES, BANK_FEES_INSUFFICIENT_FUNDS, INCOME_OTHER_INCOME. Read by the same measures that read Plaid's (nsf_count_12m counts the two bank-fee codes); other codes are kept as a categorisation hint. Optional: without it the description is read.

category_sourcestring

Where category came from, e.g. plaid, stripe_fc, partner. Recorded with the transaction; optional.

balancesarray · BankFeedIngestBalanceBankFeedIngestBalance

Reported closing balances; intermediate days are interpolated.

5 fields

account_idstringrequired

The account_id this balance snapshot belongs to.

as_ofstring · daterequired

The calendar day this closing balance applies to.

current_balance_centsintegerrequired

Closing balance on as_of, in cents.

currencystring

Three-letter ISO currency code of the balance. Underwriting reads balances in the merchant business's own currency only; balances in any other currency are stored and left out of the measures, never converted.

typestring

Account kind (cash or credit).

One of: cash, credit

Responses

201Successful Response

Schema: SuccessEnvelope_BankFeedIngestResponse_

successboolean
messagestring
codestring
dataBankFeedIngestResponse

400Bad Request - Invalid input

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

401Unauthorized - Missing or expired token, an MCP OAuth token used against the REST API, or no access to this business

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

403Forbidden - Insufficient permissions

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

404Not Found - Resource does not exist

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

422Validation Error

Schema: ErrorResponse

errorstringrequired: Error category: validation_error, unauthorized, forbidden, not_found, conflict, rate_limited, server_error, or service_unavailable.
messagestringrequired: Human-readable explanation, safe to show to end users.
codestringrequired: Stable machine-readable code in CATEGORY_NNN form (e.g. NOT_FOUND_006, AUTH_010, GEN_002).
request_idstring: Correlation id for support requests. Echoes the x-request-id request header when one was supplied.
errorsobject: Field-level validation messages keyed by field name. Present on 400/422 validation failures only.

Code samples

POST/api/v1/credit/bank-feeds/{bank_feed_id}/ingest

bash

curl -X POST 'https://api.ondayzero.com/api/v1/credit/bank-feeds/{bank_feed_id}/ingest' \
  -H 'Authorization: Bearer dz_your_token' \
  -H 'x-business-id: YOUR_BUSINESS_ID' \
  -H 'Content-Type: application/json' \
  -d '{
  "accounts": [],
  "transactions": [],
  "balances": []
}'