> ## Documentation Index
> Fetch the complete documentation index at: https://direct-api.reap.global/llms.txt
> Use this file to discover all available pages before exploring further.

# Polling and waiting

> Every poll cadence and stop condition in the Business Account API, collected in one place.

The Business Account API is asynchronous in a few places: a wallet can still
be creating, a transfer can still be settling, an approver can still be
deciding. There are no webhooks yet, so poll list endpoints instead. This
page collects every cadence and its stop condition so automated jobs can use
one reference.

## Cadences

| What you're waiting for | How to poll | When to escalate |
| - | - | - |
| A Treasury crypto deposit | `GET /treasury/transactions` every 30 to 60 seconds until `COMPLETED` | Still `PENDING`, missing, or no longer listed 30 minutes after it was sent: contact Reap support with the `transactionHash` |
| A Treasury bank transfer | `GET /treasury/transactions` every few minutes until `COMPLETED` | Still `PENDING` or no longer listed once the reconciliation window has passed (a few minutes with the Reference ID, or the 1 to 2 business days manual matching can take, counted from when the funds land in Reap's bank account): contact Reap support with the `referenceId` |
| A wallet address that is `IN_PROGRESS` | `GET /treasury/funding-instructions` again after `retryAfterSeconds` until `status` is `READY` | Never send funds before `READY`; if it stays `IN_PROGRESS` after 30 minutes, contact Reap support |
| An approval (`202` `pendingApproval`) | `GET /cards?title=<the title you chose>` until the card appears | Approvals are decided by humans in the dashboard; there is no API timeout. See [How do I set up approval workflows for my team?](https://support.reap.global/hc/en-us/articles/13939633575567-How-do-I-set-up-approval-workflows-for-my-team) in the Help Center and [Approvals](/concepts/approvals.md) |
| Connectivity checks | `GET /health` | Any `5xx` or timeout: retry; it needs a key but no scope |

## Rules that apply everywhere

* Never loop card creation without an `Idempotency-Key`; on `429`, back off
  and retry with the same key.
* `Idempotency-Key` responses are replayed for 24 hours, so a retry with the
  same key returns the original result instead of a duplicate. See
  [Idempotency](/api-reference/idempotency.md).
* A page can hold fewer items than `meta.itemsPerPage`; keep requesting
  `page` until `meta.totalPages`. See [Pagination](/api-reference/pagination.md).
* For `CARD` deposits, rejected transfers are removed from history and never
  appear as `REJECTED` or `FAILED`; a missing row alone does not prove
  rejection, so check all pages and the date filters.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.