# Going live

> What to check before you put the API in front of real customers.

Section: Guides
Source: https://statementbear.com/docs/going-live
Product: StatementBear statement parsing API, $0.49 per document, 25 free.

---

Check these before real traffic.

1. **Send an `Idempotency-Key` on every request**, generated once per document and reused by every attempt. Without it, a timeout you retry is a second charge. See [Idempotency and retries](https://statementbear.com/docs/idempotency).
2. **Set a client timeout of at least 180 seconds.** A long statement takes tens of seconds to parse, and a 30 second default turns a success into a retry.
3. **Filter on `account.type` before summing credits as income.** See [Amounts and directions](https://statementbear.com/docs/amounts-and-directions).
4. **Branch on `verification.reconciled`** and route anything false to a person. See [Verification](https://statementbear.com/docs/verification).
5. **Iterate `accounts`** rather than reading `accounts[0]`, and keep them separate. See [Accounts and periods](https://statementbear.com/docs/accounts-and-periods).
6. **Branch on `error.code`**, not on the message or a substring of it.
7. **Keep four documents in flight or fewer**, or handle `429` with a short backoff. See [Limits](https://statementbear.com/docs/api/limits).
8. **Store `doc.id`** against whatever you parsed for. It is the handle for any support question later.

## Volume

Every organisation has a monthly document cap, which stops a runaway loop turning into an invoice. There is nothing to buy. Email [api@statementbear.com](mailto:api@statementbear.com) with your expected volume and we raise it before you hit it.

## Support

[api@statementbear.com](mailto:api@statementbear.com), with the `documentId` if there is one.

---

All documentation: https://statementbear.com/docs/llms.txt
Questions: api@statementbear.com