BRAccount API Log
One row per API call: who called, which endpoint, HTTP status and how long it took. No ledger effect.
In detail
The BRAccount API Log keeps one row for every call made with a BRAccount API Key: which key, which endpoint, the HTTP status, how long the call took, and the document it created or read. It is written automatically and cannot be edited, and it has no ledger effect. It is the first place to look when an integration says it failed: a 401 means the key is wrong or revoked, a 403 means the scope is missing, a 422 means the document was rejected by a validation rule, and a 200 with no document means the call was a read. It also gives a plain audit trail of who created what through the API.
How to record it in BRAccount
- 01Go to API > BRAccount API Log.
- 02Filter by the API key or by status not equal to 200.
- 03Open a failing row and read the endpoint, the status and the error text.
- 04Fix the key, scope or document data on the integration side.
- 05Confirm the retry shows 200 and the created document name.
When to use it
Read only; check it when an integration reports errors.
Example from the demo books
A sales invoice create call returned 200 in 340 ms.