Developers

Connect Billabex to what you already use

Invoices reach Billabex through several channels at once, and the agent takes it from there. Three ways to feed it and drive it: a REST API, an MCP server for AI assistants, and no-code connectors.

Authentication
OAuth 2.1 with PKCE
Contract
OpenAPI 3.0, 76 operations
Permissions
18 least-privilege scopes

Three ways to connect Billabex

Each one reaches the same business objects: customer accounts, contacts, invoices, credit notes, follow-ups and tasks. Which one you pick depends on who is calling, your application, an AI assistant, or a workflow built without code.

Public REST API

For a deterministic application integration, from your ERP, your billing tool, or your own scripts.

  • OAuth 2.1 authorization with PKCE, no client-side secret
  • Cursor pagination and filters on every list endpoint
  • Rate limits announced in the response headers
  • JSON errors with a stable code and a resolution hint
Make your first call

MCP server

So an AI assistant can read the context of an account and act under your supervision, over Streamable HTTP.

  • Works with Claude, ChatGPT, Dust and other MCP clients
  • Same OAuth 2.1 authorization as the API, same permissions
  • Sensitive actions ask for an explicit confirmation
  • Capabilities are discovered on connection, not from a frozen catalogue
Connect an assistant

No-code connectors

To assemble a scenario without writing code, when the tool that needs to talk to Billabex already has its place in your stack.

  • Official community node for n8n, published as open source
  • Make and Zapier apps using the Billabex OAuth connection
  • The rights granted to the connection bound what it can do
  • No credential to copy between tools
Browse the integration catalogue

What you can build

The cases below are the ones the API serves in production today. Endpoints, parameters and schemas live on the developer portal.

Sync a billing source

Push accounts, contacts, invoices and credit notes from a tool Billabex does not connect natively, using a source identifier as the reconciliation key.

Track receivables without opening the app

Read the aging balance, per-account balances and payment promises to feed an internal dashboard or an existing report.

Answer what the agent asks

List open tasks, answer them from your own tool, and close them once the missing information has been provided.

Replay the conversation history

Retrieve the follow-ups sent and the replies received, with their delivery status, for archiving or auditing.

Record a payment

Update the paid amount on an invoice or record an announced payment, so the next follow-up takes it into account.

See who did what

Read the organization audit journal, one entry per successful command, filterable by account and by actor.

A question about your integration? Let's talk.

Tell us which source tool you use and what you want to automate, and we will tell you where to start.

Contact the teamNo commitment. 5 min setup.