# Bank Deposits — DayZero API 5 endpoints. OpenAPI for just this tag: https://www.ondayzero.com/docs/reference/bank-deposits/openapi.json · HTML: https://www.ondayzero.com/docs/reference/bank-deposits · All tags: https://www.ondayzero.com/docs/reference/index.md ## Endpoints - `GET /api/v1/bank-deposits` — List bank deposits - `POST /api/v1/bank-deposits` — Create bank deposit - `GET /api/v1/bank-deposits/undeposited` — List undeposited funds - `GET /api/v1/bank-deposits/{deposit_id}` — Get bank deposit - `POST /api/v1/bank-deposits/{deposit_id}/void` — Void bank deposit --- ## GET /api/v1/bank-deposits > List bank deposits - **Tag:** bank-deposits - **Operation ID:** `list_bank_deposits` ### Description List bank deposits for the business. ### Authentication Bearer token in `Authorization` header. Required header: `x-business-id: `. ### Parameters - `status` (query, string, optional) — Filter by status: posted or void. - `cursor` (query, string, optional) — Cursor for pagination - `limit` (query, integer, optional) — Pagination limit - `direction` (query, string, optional) — Pagination direction: 'next' or 'prev' - `include_total_count` (query, boolean, optional) — Whether to include total count (expensive - avoid if possible) - `sort_by` (query, string, optional) — Column name to sort by (e.g. 'created_at', 'amount', 'name'). When changing sort, reset cursor to None. - `descending` (query, boolean, optional) — Sort direction: true for descending (newest/largest first), false for ascending ### Responses #### 200 — Successful Response Schema: `SuccessEnvelope_BankDepositsListResponse_` - `success` (boolean) - `message` (string) - `code` (string) - `data` (BankDepositsListResponse) #### 401 — Unauthorized - Missing or expired token, an MCP OAuth token used against the REST API, or no access to this business Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 403 — Forbidden - Insufficient permissions Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 422 — Validation Error Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. ### Code samples #### cURL ```bash curl -X GET 'https://api.ondayzero.com/api/v1/bank-deposits' \ -H 'Authorization: Bearer dz_your_token' \ -H 'x-business-id: YOUR_BUSINESS_ID' ``` #### JavaScript ```javascript const response = await fetch('https://api.ondayzero.com/api/v1/bank-deposits', { method: 'GET', headers: { Authorization: 'Bearer dz_your_token', 'x-business-id': 'YOUR_BUSINESS_ID', }, }); const data = await response.json(); ``` #### Python ```python import httpx headers = { "Authorization": "Bearer dz_your_token", "x-business-id": "YOUR_BUSINESS_ID", } response = httpx.get("https://api.ondayzero.com/api/v1/bank-deposits", headers=headers) data = response.json() ``` ### See also - HTML version: https://www.ondayzero.com/docs/reference/bank-deposits/list-bank-deposits - OpenAPI slice: https://www.ondayzero.com/docs/reference/bank-deposits/list-bank-deposits/openapi.json - Other endpoints in **bank-deposits**: https://www.ondayzero.com/docs/reference/bank-deposits (markdown bundle: https://www.ondayzero.com/docs/reference/bank-deposits.md, OpenAPI: https://www.ondayzero.com/docs/reference/bank-deposits/openapi.json) - Endpoint catalog: https://www.ondayzero.com/docs/reference/index.md --- ## POST /api/v1/bank-deposits > Create bank deposit - **Tag:** bank-deposits - **Operation ID:** `create_bank_deposit` ### Description Group undeposited receipts and ad-hoc lines into a bank deposit. ### Authentication Bearer token in `Authorization` header. Required header: `x-business-id: `. ### Request body Schema: `BankDepositCreateRequest` - `deposit_to_ledger_id` (string · required) — Bank/cash account the money lands in. - `deposit_date` (string · date) — Deposit date. Defaults to today. - `sales_receipt_ids` (array · string) — Undeposited sales receipts to group into this deposit. - `other_lines` (array · OtherDepositLine) → `OtherDepositLine` — Optional ad-hoc deposit lines (non-undeposited sources). - `from_ledger_id` (string · required) — Account credited for this line (e.g. interest income). - `description` (string) - `amount` (integer · required) — Line amount in cents. - `number` (string) - `memo` (string) - `currency` (string) ### Responses #### 201 — Successful Response Schema: `SuccessEnvelope_BankDepositResponse_` - `success` (boolean) - `message` (string) - `code` (string) - `data` (BankDepositResponse) #### 400 — Bad Request - Invalid input Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 401 — Unauthorized - Missing or expired token, an MCP OAuth token used against the REST API, or no access to this business Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 403 — Forbidden - Insufficient permissions Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 404 — Not Found - Resource does not exist Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 422 — Validation Error Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. ### Code samples #### cURL ```bash curl -X POST 'https://api.ondayzero.com/api/v1/bank-deposits' \ -H 'Authorization: Bearer dz_your_token' \ -H 'x-business-id: YOUR_BUSINESS_ID' \ -H 'Content-Type: application/json' \ -d '{ "deposit_to_ledger_id": "string" }' ``` #### JavaScript ```javascript const response = await fetch('https://api.ondayzero.com/api/v1/bank-deposits', { method: 'POST', headers: { Authorization: 'Bearer dz_your_token', 'x-business-id': 'YOUR_BUSINESS_ID', 'Content-Type': 'application/json', }, body: JSON.stringify({ "deposit_to_ledger_id": "string" }), }); const data = await response.json(); ``` #### Python ```python import httpx headers = { "Authorization": "Bearer dz_your_token", "x-business-id": "YOUR_BUSINESS_ID", } payload = {'deposit_to_ledger_id': 'string'} response = httpx.post("https://api.ondayzero.com/api/v1/bank-deposits", headers=headers, json=payload) data = response.json() ``` ### See also - HTML version: https://www.ondayzero.com/docs/reference/bank-deposits/create-bank-deposit - OpenAPI slice: https://www.ondayzero.com/docs/reference/bank-deposits/create-bank-deposit/openapi.json - Other endpoints in **bank-deposits**: https://www.ondayzero.com/docs/reference/bank-deposits (markdown bundle: https://www.ondayzero.com/docs/reference/bank-deposits.md, OpenAPI: https://www.ondayzero.com/docs/reference/bank-deposits/openapi.json) - Endpoint catalog: https://www.ondayzero.com/docs/reference/index.md --- ## GET /api/v1/bank-deposits/undeposited > List undeposited funds - **Tag:** bank-deposits - **Operation ID:** `list_undeposited` ### Description List posted sales receipts in Undeposited Funds awaiting deposit. ### Authentication Bearer token in `Authorization` header. Required header: `x-business-id: `. ### Responses #### 200 — Successful Response Schema: `SuccessEnvelope_UndepositedItemsResponse_` - `success` (boolean) - `message` (string) - `code` (string) - `data` (UndepositedItemsResponse) #### 401 — Unauthorized - Missing or expired token, an MCP OAuth token used against the REST API, or no access to this business Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 403 — Forbidden - Insufficient permissions Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 422 — Validation Error Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. ### Code samples #### cURL ```bash curl -X GET 'https://api.ondayzero.com/api/v1/bank-deposits/undeposited' \ -H 'Authorization: Bearer dz_your_token' \ -H 'x-business-id: YOUR_BUSINESS_ID' ``` #### JavaScript ```javascript const response = await fetch('https://api.ondayzero.com/api/v1/bank-deposits/undeposited', { method: 'GET', headers: { Authorization: 'Bearer dz_your_token', 'x-business-id': 'YOUR_BUSINESS_ID', }, }); const data = await response.json(); ``` #### Python ```python import httpx headers = { "Authorization": "Bearer dz_your_token", "x-business-id": "YOUR_BUSINESS_ID", } response = httpx.get("https://api.ondayzero.com/api/v1/bank-deposits/undeposited", headers=headers) data = response.json() ``` ### See also - HTML version: https://www.ondayzero.com/docs/reference/bank-deposits/list-undeposited - OpenAPI slice: https://www.ondayzero.com/docs/reference/bank-deposits/list-undeposited/openapi.json - Other endpoints in **bank-deposits**: https://www.ondayzero.com/docs/reference/bank-deposits (markdown bundle: https://www.ondayzero.com/docs/reference/bank-deposits.md, OpenAPI: https://www.ondayzero.com/docs/reference/bank-deposits/openapi.json) - Endpoint catalog: https://www.ondayzero.com/docs/reference/index.md --- ## GET /api/v1/bank-deposits/{deposit_id} > Get bank deposit - **Tag:** bank-deposits - **Operation ID:** `get_bank_deposit` ### Description Get details of a specific bank deposit. ### Authentication Bearer token in `Authorization` header. Required header: `x-business-id: `. ### Parameters - `deposit_id` (path, string, required) ### Responses #### 200 — Successful Response Schema: `SuccessEnvelope_BankDepositResponse_` - `success` (boolean) - `message` (string) - `code` (string) - `data` (BankDepositResponse) #### 401 — Unauthorized - Missing or expired token, an MCP OAuth token used against the REST API, or no access to this business Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 403 — Forbidden - Insufficient permissions Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 404 — Not Found - Resource does not exist Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 422 — Validation Error Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. ### Code samples #### cURL ```bash curl -X GET 'https://api.ondayzero.com/api/v1/bank-deposits/{deposit_id}' \ -H 'Authorization: Bearer dz_your_token' \ -H 'x-business-id: YOUR_BUSINESS_ID' ``` #### JavaScript ```javascript const response = await fetch('https://api.ondayzero.com/api/v1/bank-deposits/{deposit_id}', { method: 'GET', headers: { Authorization: 'Bearer dz_your_token', 'x-business-id': 'YOUR_BUSINESS_ID', }, }); const data = await response.json(); ``` #### Python ```python import httpx headers = { "Authorization": "Bearer dz_your_token", "x-business-id": "YOUR_BUSINESS_ID", } response = httpx.get("https://api.ondayzero.com/api/v1/bank-deposits/{deposit_id}", headers=headers) data = response.json() ``` ### See also - HTML version: https://www.ondayzero.com/docs/reference/bank-deposits/get-bank-deposit - OpenAPI slice: https://www.ondayzero.com/docs/reference/bank-deposits/get-bank-deposit/openapi.json - Other endpoints in **bank-deposits**: https://www.ondayzero.com/docs/reference/bank-deposits (markdown bundle: https://www.ondayzero.com/docs/reference/bank-deposits.md, OpenAPI: https://www.ondayzero.com/docs/reference/bank-deposits/openapi.json) - Endpoint catalog: https://www.ondayzero.com/docs/reference/index.md --- ## POST /api/v1/bank-deposits/{deposit_id}/void > Void bank deposit - **Tag:** bank-deposits - **Operation ID:** `void_bank_deposit` ### Description Void a deposit, reversing the entry and releasing its receipts. ### Authentication Bearer token in `Authorization` header. Required header: `x-business-id: `. ### Parameters - `deposit_id` (path, string, required) ### Responses #### 201 — Successful Response Schema: `SuccessEnvelope_BankDepositResponse_` - `success` (boolean) - `message` (string) - `code` (string) - `data` (BankDepositResponse) #### 400 — Bad Request - Invalid input Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 401 — Unauthorized - Missing or expired token, an MCP OAuth token used against the REST API, or no access to this business Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 403 — Forbidden - Insufficient permissions Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 404 — Not Found - Resource does not exist Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. #### 422 — Validation Error Schema: `ErrorResponse` - `error` (string · required) — Error category: `validation_error`, `unauthorized`, `forbidden`, `not_found`, `conflict`, `rate_limited`, `server_error`, or `service_unavailable`. - `message` (string · required) — Human-readable explanation, safe to show to end users. - `code` (string · required) — Stable machine-readable code in `CATEGORY_NNN` form (e.g. `NOT_FOUND_006`, `AUTH_010`, `GEN_002`). - `request_id` (string) — Correlation id for support requests. Echoes the `x-request-id` request header when one was supplied. - `errors` (object) — Field-level validation messages keyed by field name. Present on 400/422 validation failures only. ### Code samples #### cURL ```bash curl -X POST 'https://api.ondayzero.com/api/v1/bank-deposits/{deposit_id}/void' \ -H 'Authorization: Bearer dz_your_token' \ -H 'x-business-id: YOUR_BUSINESS_ID' ``` #### JavaScript ```javascript const response = await fetch('https://api.ondayzero.com/api/v1/bank-deposits/{deposit_id}/void', { method: 'POST', headers: { Authorization: 'Bearer dz_your_token', 'x-business-id': 'YOUR_BUSINESS_ID', }, }); const data = await response.json(); ``` #### Python ```python import httpx headers = { "Authorization": "Bearer dz_your_token", "x-business-id": "YOUR_BUSINESS_ID", } response = httpx.post("https://api.ondayzero.com/api/v1/bank-deposits/{deposit_id}/void", headers=headers) data = response.json() ``` ### See also - HTML version: https://www.ondayzero.com/docs/reference/bank-deposits/void-bank-deposit - OpenAPI slice: https://www.ondayzero.com/docs/reference/bank-deposits/void-bank-deposit/openapi.json - Other endpoints in **bank-deposits**: https://www.ondayzero.com/docs/reference/bank-deposits (markdown bundle: https://www.ondayzero.com/docs/reference/bank-deposits.md, OpenAPI: https://www.ondayzero.com/docs/reference/bank-deposits/openapi.json) - Endpoint catalog: https://www.ondayzero.com/docs/reference/index.md