Integration

Billingo integration

Billingo is a Hungarian online invoicing service that reports invoices to the NAV Online Számla system. Issue invoices, proformas, advance invoices, drafts and receipts, cancel or modify them, download their PDF, email them, record payments and check their NAV reporting status; manage partners (customers), products, bank accounts, document blocks (invoice pads) and spendings (incoming invoices); validate Hungarian tax numbers, read exchange rates and run accounting exports. Authentication is a Billingo API v3 key, generated under Settings, Integrations, API keys in Billingo and sent in the X-API-KEY header; the account needs an API subscription.

Connect Billingo How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Billingo.Built from the 54 Billingo tools below, on the connection you add once.

What you can do with Billingo

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Bank account, 5 operations

create_bank_accountCreate bank accountPOSTAdds a bank account to your Billingo account; it can then be printed on invoices through bank_account_id. Returns the new bank account.
delete_bank_accountDelete bank accountDELETEDelete an existing bank account.
get_bank_accountGet bank accountGETRetrieves the details of an existing bank account.
list_bank_accountsList bank accountsGETLists your bank accounts, newest first, in pages (data, total, current_page, last_page).
update_bank_accountUpdate bank accountPUTUpdates one of your bank accounts. name, account_number and currency are required; returns the updated bank account.

Document, 5 operations

convert_draft_to_documentConvert draft to documentPUTTurns a draft into a real document (invoice, proforma or advance invoice), with the same fields as create_document. Only works on a draft.
create_documentCreate documentPOSTCreates a document: an invoice, proforma, advance invoice or draft. Needs a partner_id, a block_id, dates, payment method, language, currency and the line items. Returns the created document with its invoice_number.
delete_draft_documentDelete draft documentDELETEDeletes a document whose type allows it, such as a draft. To void an issued invoice, use cancel_document.
get_documentGet documentGETReturns one document with its partner, line items, totals, payment status, NAV reporting status and related documents.
list_documentsList documentsGETLists your documents (invoices, proformas, receipts and more), newest first, in pages. Filter by block, partner, payment method or status, type, dates, number range, text or last modification.

Partner, 5 operations

create_partnerCreate partnerPOSTCreates a partner (customer or supplier) with name, address, emails, tax number and bank details. Returns the partner with its id, used as partner_id on documents.
delete_partnerDelete partnerDELETEDelete an existing partner.
get_partnerGet partnerGETReturns one partner with its address, emails, tax number, bank details and billing settings.
list_partnersList partnersGETLists your partners (customers and suppliers), newest first, in pages, optionally filtered by a search text.
update_partnerUpdate partnerPUTUpdates a partner with the given fields and returns the updated partner.

Product, 5 operations

create_productCreate productPOSTCreates a product with name, unit, unit price, currency and VAT key. Its id can then be used as product_id in document line items.
delete_productDelete productDELETEDelete an existing product.
get_productGet productGETReturns one product with its prices, VAT key, unit, EAN and SKU.
list_productsList productsGETLists your products, newest first, in pages, optionally filtered by name, EAN or SKU.
update_productUpdate productPUTUpdates a product. name, currency, vat and unit are required; returns the updated product.

Spending, 5 operations

create_spendingCreate spendingPOSTRecords a spending (an incoming invoice or other cost) with its totals, VAT, category, dates and payment method. Returns the spending.
delete_spendingDelete spendingDELETEDeletes a spending.
get_spendingGet spendingGETReturns one spending with its supplier partner, totals, VAT, dates, category and line items.
list_spendingsList spendingsGETLists your spendings (incoming invoices and other costs), ordered by due date, filtered by date range, payment status, source, category, currency or payment method.
update_spendingUpdate spendingPUTUpdates a spending with the given fields and returns it.

Payment, 3 operations

delete_document_paymentsDelete document paymentsDELETEDeletes every payment recorded on a document.
list_document_paymentsList document paymentsGETLists the payments recorded on a document: date, amount, payment method, voucher number and exchange rate.
update_document_paymentsUpdate document paymentsPUTUpdates the payment history of a document with the given list of payments and returns the stored payments.

Document block, 2 operations

create_document_blockCreate document blockPOSTCreates a document block (invoice pad) that sets the prefix, numbering and email sender of the documents issued from it.
list_document_blocksList document blocksGETLists your document blocks (invoice pads), newest first. A block's id is the block_id that create_document and create_receipt require.

Document export, 2 operations

create_document_exportCreate document exportPOSTStarts an export of your documents for a date range in a given format (CSV, Excel, NAV XML or an accounting program's format). Returns the export id; follow it with get_document_export_status, then download_document_export.
download_document_exportDownload document exportGETDownloads the file of a finished export started by create_document_export (CSV, Excel, XML or an accounting program's format). Check get_document_export_status for success first.

Receipt, 2 operations

convert_draft_to_receiptConvert draft to receiptPUTTurns a draft into a receipt, with the same fields as create_receipt. Returns the receipt.
create_receiptCreate receiptPOSTCreates a receipt (nyugta), optionally for a known partner or a named buyer with email addresses. Returns the created document.

Archive, 1 operation

archive_proformaArchive proformaPUTArchives a proforma (payment request) document.

Cancel, 1 operation

cancel_documentCancel documentPOSTCancels (reverses) an issued document by creating its cancellation document, optionally emailing the given recipients. Returns the cancellation document.

Check tax number, 1 operation

check_tax_numberCheck tax numberGETChecks a Hungarian tax number against NAV and, when valid, returns the taxpayer's name, short name and addresses.

Convert legacy id, 1 operation

convert_legacy_idConvert legacy idGETConverts an identifier from the old Billingo API v2 into the matching API v3 identifier.

Copy, 1 operation

copy_documentCopy documentPOSTCreates a copy of a document and returns the new document.

Create from proforma, 1 operation

create_document_from_proformaCreate document from proformaPOSTCreates a final document, usually an invoice, from a proforma, optionally with new dates, format and comment. Returns the new document.

Create modification document, 1 operation

create_modification_documentCreate modification documentPOSTCreates a modification document for an issued invoice, with corrected line items, due date, payment method or comment. Returns the new document.

Currencie, 1 operation

get_exchange_rateGet exchange rateGETReturns the exchange rate between two currencies, optionally for a given date.

Download, 1 operation

download_document_pdfDownload document pdfGETDownloads the document as a PDF file. If Billingo has not finished generating the PDF it answers 202 with a message instead of the file; call again a little later.

Gues, 1 operation

find_or_create_partnerFind or create partnerPOSTLooks for an existing partner matching the given data and returns it; if none matches, creates a new partner from the data.

Online szamla, 1 operation

get_online_szamla_statusGet online szamla statusGETReturns the NAV Online Számla reporting status of a document: the NAV transaction id, the status and any validation messages.

Organization, 1 operation

get_organizationGet organizationGETReturns data about your own organization: tax number, subscription expiry and features, and whether NAV connection is set up.

Po, 1 operation

download_document_pos_pdfDownload document pos pdfGETDownloads a document as a PDF formatted for a POS receipt printer, 58 or 80 mm wide.

Poll, 1 operation

get_document_export_statusGet document export statusGETReturns the state of an export started by create_document_export: pending, processing, success, warning or fail, with a message. Download the file with download_document_export once it succeeds.

Public url, 1 operation

get_document_public_urlGet document public urlGETReturns a public URL where the document can be downloaded.

Quantity, 1 operation

get_product_stock_quantityGet product stock quantityGETReturns the quantity of a product available in the default warehouse.

Reminder, 1 operation

list_document_remindersList document remindersGETLists the email reminders of a document, grouped as sent reminders (with delivery and open status), upcoming reminders and postal mail sent.

Send, 1 operation

send_documentSend documentPOSTEmails the document to the given addresses and returns the addresses it was sent to.

Time, 1 operation

get_server_timeGet server timeGETReturns the Billingo server time as a Unix epoch, a formatted string, a W3C timestamp and the time zone.

Vendor, 1 operation

get_document_by_vendor_idGet document by vendor idGETFinds a document by the vendor_id you gave it when creating it (your own external identifier, such as a webshop order id).

Use Billingo from Claude Code, Cursor or Codex

Connect Billingo in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Billingo operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Billingo

Create your workspace
Sign up free. Nothing to install.
Connect Billingo once
Add your Billingo connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.