Can I update a bill's status through this API?

Yes. POST /bills/update-status/{id} advances the bill, and GET /bills/get-approval-steps/{id} returns the configured approval chain so you can confirm the next required approver before transitioning.

What are the rate limits for the LEXZUR Money API?

The OpenAPI spec does not publish explicit rate limits. Limits are governed by your LEXZUR plan tier - contact the LEXZUR support team for your firm's quota before high-volume reconciliation imports.

How do I run a bank reconciliation through Jentic?

Run pip install jentic, then search 'run a bank reconciliation in lexzur'. Jentic returns the bank-reconciliations operations with their input schemas - load the schema, submit the transactions, and execute. The agent never sees the bearer token.

Can I bulk-import accounts during a migration?

Yes. POST /accounts/import accepts a batch payload and reports per-row success or failure. Use this rather than calling POST /accounts in a loop, both for performance and for the consolidated import diagnostics.

What custom fields can I configure on bills?

Custom fields are defined via /bill-custom-fields and read via /bill-custom-fields/{id}. Once created, the fields appear on bill payloads so firm-specific metadata (matter type, billing partner, retainer reference) can be enforced through the API.

Can I limit what my agent is allowed to do with the LEXZUR Money API?

Yes. Because you run your own self-hosted Jentic One instance, your rules decide which LEXZUR Money operations and credentials the agent may use. You choose the operations it can call, so writes such as updating a bill status via POST /bills/update-status/{id} or bulk-importing accounts via POST /accounts/import are excluded unless you add them. Since LEXZUR puts bill and client ids in the URL path, like /bills/get-approval-steps/{id} and /clients/{id}/accounts, a rule can pin the agent to specific bills or client trust accounts.