Official clients for the FacturX API: check an invoice with a dry run, convert it to a Factur-X PDF/A-3 file, validate it — from Python, Node.js, a command line, or an MCP-compatible assistant.
Directory | Package | Registry | What it is |
| PyPI | Python client and the | |
| npm | Node.js client (ESM, TypeScript types) | |
| PyPI | MCP server (registry name | |
— | — | Runnable examples with their recorded output |
Status: alpha. facturx-api and facturx-mcp 0.1.1 are on PyPI (pip install facturx-api, pip install facturx-mcp);
@facturxapi/sdk 0.1.1 is on npm (npm install @facturxapi/sdk). See RELEASING.md.
Production by default (from 0.1.2): the host is https://api.facturxapi.com unless you pass base_url / baseUrl or set FACTURX_BASE_URL; it must be https. In 0.1.1 the host is required.
A final file is checked, not assumed. A dry run reads the API's generationReadiness; a conversion is only
reported as done when the final file is present, not on the HTTP status alone.
One idempotency key per operation, and signed download URLs are fetched without your API key.
No automatic retry of 409 / 503 answers: the caller decides.
The examples in examples/ were recorded against the staging host and say so; they will move to the
production host with the first release.
Related MCP server: eleata e-invoice MCP server
cd python && PYTHONPATH=src python -m unittest discover -s tests -v && ruff check .
cd node && npm test
cd mcp && pip install ../python . pytest && pytest testsSee SECURITY.md. Releases use trusted publishing (OIDC): no registry token is stored in this
repository.
MIT.
Final conversion: COSTS 1 invoice of the account quota (refunded by the API when no file is produced). Call it only after facturx_dry_run returned ready=true. Writes factur-x.pdf and factur-x.xml into out_dir and returns their paths, sizes, sha256, the verified target and the idempotency_key. If the call fails without an answer, call again with the SAME idempotency_key: the API will not charge twice.
Inputs: invoice (required), out_dir (required), output, idempotency_key, +1 more. Returns: object
Check a complete ERP invoice JSON WITHOUT producing a file and WITHOUT using quota. Use it first, every time. Returns ready (true only when generationReadiness.status is 'ready'; success=false can still be ready), the readiness detail, request_id and idempotency_key.
Inputs: invoice (required), output, validation_target. Returns: object
Explain an EN16931 / France 2026 rule (e.g. BR-CO-15), a business term (e.g. BT-1) or an invoice JSON path (e.g. totals.gross): returns the matching invoice fields from the API's public integration contract (JSON path, BT, rule, CII XPath, requirement). Free, no API key needed. API error codes (409/503 …) are not in this public source yet.
Inputs: code_or_rule (required). Returns: object
Validate an existing Factur-X PDF or CII XML file from the local disk against validation_target (default en16931, the same target as facturx_dry_run and facturx_convert; pass france_2026 to check the invoice is ready for a French PA, plateforme agréée). Returns valid, validationStatus, profile, target and the first errors as reported by the API. Counts 1 invoice of the account quota when the API returns a report.
Inputs: file_path (required), validation_target. Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 4 tools
Each tool has a clearly distinct role: dry-run readiness check on ERP JSON, final file generation, validation of existing PDF/XML files, and error/rule explanation. The descriptions explicitly enforce sequencing (dry_run before convert) and distinguish input types, leaving little room for misselection.
All tools consistently use the facturx_ prefix followed by snake_case verb or verb_noun names: dry_run, convert, validate, explain_error. The pattern is predictable throughout the small set.
Four tools are well scoped for a focused e-invoicing conversion server: preflight, generate, validate, and explain. Each tool earns its place, and there is no redundant or trivial surface.
The core lifecycle is covered: readiness check, conversion, validation, and error explanation. Minor gaps exist, such as no tool for account/quota status, listing supported validation targets, or extracting invoice fields from an existing file, but these are workaroundable.
Validate, extract, repair and generate French Factur-X / EN16931 invoices via AgentForge API
Validate, generate & convert EU e-invoices (UBL, CII, XRechnung, Factur-X) — EN 16931 pre-validated.
Create, validate, convert & extract compliant e-invoices (UBL, Factur-X, ZUGFeRD, XRechnung)
Generate & validate EN 16931 e-invoices (Factur-X, ZUGFeRD, XRechnung); verification certificates
