Integrations

Every path below speaks the same Beliq API: one request envelope, one JSON error shape, and the same operations, whether you call it directly over REST, from an SDK or developer tool, a no-code connector, a shop plugin, or your accounting tool. Pick the path that fits how you already work.

There are five ways to reach Beliq. They differ only in how you call it, never in what comes back.

Call Beliq from your own codebase, an AI agent, the terminal, or your CI pipeline. Each one wraps the same API and sniffs XML versus PDF from the bytes, so you write less plumbing.

Build compliant-invoice steps inside the workflow tool you already run. Each connector maps your fields to the Beliq API and hands the result to the next step, no code required.

Turn store orders into compliant invoices without leaving your shop. Each plugin maps an order to an EN 16931 invoice, generates the document through Beliq, and stores it on the order. Generation is off until you enable it, and defaults to business orders.

Modern accounting tools generate XRechnung and ZUGFeRD natively, but they trust their own output. Beliq adds an independent, authority-pinned second opinion: validate what your tool emits before it goes out, and convert it when the counterparty needs a different format. Beliq does not re-generate the invoice or send it.

Every operation maps to one API endpoint. The REST API, the SDKs, the MCP server, the CLI, and the no-code connectors surface all four. The GitHub Action validates in CI; the e-commerce plugins run one direction, order to invoice, so they generate and validate; and the accounting worker validates and converts what your tool emits.

✓ supported, - not applicable. Every path also uses GET /v1/me, a zero-quota credential check, to confirm a key works.