Introduction

Welcome to Buk Finance API! Here you will find a way to connect to your accounts receivable, accounts payable and prepaid-expenses (fondos por rendir) information for programmatic access. The documentation is designed to be as easy to understand as possible, but if you need support you can contact us at [email protected].

To use the API you need an active Buk Finance account and an API token issued by our team for your organization. The token is sent in the Authorization header exactly as delivered (see Authentication).

Base URL: https://api.bemmbo.com/v1

Endpoints

Area	Endpoint
Accounts receivable	GET /invoices/issued
Accounts receivable	GET /customers
Accounts receivable	GET /customers/{id}
Accounts receivable	GET /customers/portal-link
Accounts payable	GET /invoices/received
Accounts payable	GET /accounts-payable/prepaid-expenses
Accounts payable	GET /accounts-payable/prepaid-expenses/{id}

This reference covers the read (GET) endpoints available to integrators. Signed file links returned by GET /invoices/issued (files[].fileUrl, valid for 24 hours) redirect to the file and need no extra documentation.

What changed in 1.1

• Prepaid expenses (fondos por rendir) live under /accounts-payable/prepaid-expenses; the previously documented /prepaid-expenses path never existed.
• contacts, contact and collection pages were removed: those endpoints do not exist.
• totalAmount (received invoices) and fiscalId / overdueAmount (customers) were removed from the reference because they currently respond 400 for any value; they will return once fixed (CORE-2774, CORE-2775).
• GET /customers/{id} will respond 404 for unknown or foreign ids (currently 500, CORE-2788).
• Every page now documents the real status codes, defaults and limits, and the Authorization header format (no Bearer).

📘

A request to a URL that does not exist responds 403 with a message that mentions Credential and Signature. That is not a token problem: double-check the path against the table above.