You can find out whether beliq does what you want before you write a line of code or reach for an API key. Run a real invoice through it in the browser, read the result, and move to code only once you have decided it is worth it. The video is the short version; the walk-through is below.
Start in the browser, not in your editor
The playground runs the real engine, with no account and no key. Paste in an invoice or start from one of the samples, then run it: validate an existing file, generate one from a JSON description, parse a document back into its fields, or convert between formats. What comes back is what the API returns, because it is the same engine behind both. That is the point of starting here. You are testing the actual thing, not a sandbox that behaves differently in production.
If you would rather begin from a blank invoice, the free generator fills one in field by field and hands you a real EN 16931 file at the end, in the browser.
The result is something you can check
A generic quickstart ends when the request returns 200. beliq’s does not,
because a returned invoice is only useful if it is actually valid, and “valid”
has to mean something you can point to.
So every result names the rule sets it ran, their exact versions, and a hash of each one. A green verdict means your invoice met the tax authority’s own published definition, not beliq’s reading of it (or, where the authority publishes only a schema, that your file is valid against it), and the hashes let you confirm later that the rules that ran are the exact ones beliq pins. You see this in the playground before you have written a line of code, which is the honest way to judge a compliance tool: check the thing it claims, on your own file.
When you are ready for code
Everything you did in the browser maps to one call on the API. Validating the file you just pasted is a single POST with your key and the invoice body; generating one is a POST with the JSON you filled in. The operation is the same, you have only moved it into your own code.
The commands live in the quickstart in the docs, kept current against the API, so this post does not reprint them to go stale. Grab a key from the dashboard, follow the quickstart, and you have the same result you saw in the playground, now running where you need it. From there the same operations are available through the SDKs and no-code connectors if you would rather not call the REST API directly.
Generate, validate, parse and convert are all live today. Managed delivery, routing the finished invoice over the right EU network, is what beliq builds next; until it ships, you send the file through the access point or portal you already use.
It runs in the EU, start to finish
Whether you validate or generate, the invoice runs through beliq’s systems inside the EU, on Hetzner, with nothing crossing to the US. The Trust Center lists every subprocessor and where it is based. That holds in the playground too, so the file you test with never leaves the same boundary as the one you send in production.
Where to start
The shortest path is the one you can watch above: open the playground, run a real invoice, read the result, then take the same operation to your code when it earns it. Nothing to install, and no code to write until you have seen it work for yourself.