Magic Heidi Swiss Invoice QR Code API
★ Only Publicly Available OpenAPI DocumentFinanceAccountingapiKey1 EndpointsREST
For Agents
Generate a Swiss-compliant invoice PDF with embedded QR-bill payment slip from a single POST request.
Use for: I need to generate a Swiss invoice PDF for a freelance gig, Issue a QR-bill formatted invoice for a Swiss customer, Create an invoice with an embedded scannable payment slip, Generate a CHF invoice PDF with VAT lines for archiving
Not supported: Does not handle invoice delivery, payment reconciliation, or recurring billing - use for one-shot Swiss QR-bill PDF generation only.
Jentic publishes the only available OpenAPI specification for Magic Heidi Swiss Invoice QR Code API, keeping it validated and agent-ready. Magic Heidi exposes a single Cloud Function endpoint that generates a fully formatted Swiss invoice - including the Swiss QR-bill payment slip - as a downloadable PDF. The API targets freelancers, accountants and SMB billing tools that need to issue compliant Swiss invoices without integrating against a full accounting platform.
Install Jentic One Beta
Connect the Magic Heidi Swiss Invoice QR Code API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Magic Heidi Swiss Invoice QR Code API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmagic-heidi.cloudfunctions.net%2Fmagic-heidi" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fmagic-heidi.cloudfunctions.net%2Fmagic-heidi" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Magic Heidi Swiss Invoice QR Code API.
Generate a Swiss-compliant invoice PDF including the official QR-bill slip via POST /create_invoice_abstract_v1d
Embed payer and creditor address blocks formatted to Swiss invoicing standards
Encode the IBAN, reference number and amount inside the QR-bill so payers can scan and pay in their banking app
Return the rendered PDF binary so the caller can email or archive it directly
Customise line items, currency and VAT lines on the issued invoice
Use Cases
Patterns agents use Magic Heidi Swiss Invoice QR Code API for, with concrete tasks.
★ Freelancer Invoice Generation
Generate a polished Swiss invoice without operating a full accounting suite. POST /create_invoice_abstract_v1d takes payer details, line items, IBAN and reference, and returns a PDF with the official QR-bill section. Suitable for freelancers, consultants and small studios that bill a handful of Swiss clients each month and want a programmatic alternative to manual invoice templates.
POST /create_invoice_abstract_v1d with the client's billing address, IBAN, reference number and line items, then save the returned PDF
Embedded Billing in SMB Tools
Wire Swiss-compliant invoicing into an existing SaaS without building QR-bill rendering from scratch. The POST /create_invoice_abstract_v1d endpoint handles the precise positioning, font and reference-number rules required by SIX, returning a print-ready PDF the host app can attach to an email or store on the customer record. Useful for project tools and CRMs adding invoicing as a sidecar feature.
On project completion, POST /create_invoice_abstract_v1d with the project's totals and the client's billing block to attach a Swiss invoice PDF to the closeout email
AI Agent Invoice Issuance
Let an AI billing assistant issue a compliant Swiss invoice on demand. Through Jentic the agent searches for the invoice operation, loads the input schema for /create_invoice_abstract_v1d, and executes with credentials brokered by the vault. The agent never handles the Magic Heidi API key directly, which keeps the credential out of conversational context.
Search Jentic for 'generate a swiss invoice pdf', load /create_invoice_abstract_v1d, and execute with the user's project totals and IBAN
Key Endpoints
1 endpoints — jentic publishes the only available openapi specification for magic heidi swiss invoice qr code api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
POST
/create_invoice_abstract_v1d
Generate a Swiss invoice PDF with QR-bill
POST
/create_invoice_abstract_v1d
Generate a Swiss invoice PDF with QR-bill
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Magic Heidi Swiss Invoice QR Code API by hand means sending its API key to the europe-west6 cloud-functions host and handling the single PDF-generation call yourself. Through Jentic you install once, import the Magic Heidi Swiss Invoice QR Code API from the API Directory, store the key once, and your agent calls it.
Permission scoping
This API exposes a single operation, generating a Swiss QR-bill PDF, so you allow that one operation and the agent can do nothing beyond it. You keep the choice of whether the agent may call it at all.
Credential isolation
Your Magic Heidi key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
Intent-based discovery
Agents search Jentic by intent such as 'generate a Swiss invoice PDF', and Jentic returns the create-invoice operation with its input schema so the agent calls it without reading the GitHub README.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Magic Heidi Swiss Invoice QR Code API through Jentic.
Why is there no official OpenAPI spec for Magic Heidi Swiss Invoice QR Code API?
Magic Heidi publishes the function on GitHub but does not ship a formal OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call the Swiss invoice generator via structured tooling. It is validated against the live Cloud Function and kept up to date. Get started with Jentic One, the self-hosted execution layer.
What authentication does the Magic Heidi Swiss Invoice API use?
The API uses an API key passed as a request header (the ApiKeyAuth scheme in the spec). Through Jentic the key is held encrypted in your Jentic One instance, so an agent calls /create_invoice_abstract_v1d with a scoped token rather than handling the raw credential.
Does the Magic Heidi API generate the official Swiss QR-bill?
Yes. POST /create_invoice_abstract_v1d returns a PDF that includes the SIX-compliant QR-bill payment slip with the IBAN, amount and reference number encoded so payers can scan and pay it directly inside their banking app.
What are the rate limits for the Magic Heidi Swiss Invoice API?
Per-endpoint rate limits are not declared in the spec. Because the endpoint runs on Google Cloud Functions in europe-west6, throughput follows that platform's per-function concurrency settings. For high-volume billing use, coordinate with the Magic Heidi maintainers on dedicated quota.
How do I generate a Swiss invoice PDF through Jentic?
Run pip install jentic, search for 'generate a swiss invoice', and Jentic surfaces POST /create_invoice_abstract_v1d with its input schema. Execute with payer details, IBAN, reference number and line items, then persist the returned PDF binary to disk or storage.
Can the Magic Heidi API also send the invoice to the customer?
No. The API only generates the PDF. To deliver it, pair it with an email API such as SendGrid Mail, attaching the returned PDF to a transactional email message. The agent flow is to call Magic Heidi first, then route the binary to the chosen delivery channel.
GET STARTED