A real invoicing API, certified for Portugal

Three calls to your first certified invoice

Create a key in Settings → Developers, then create a customer and issue an invoice against it. Send prices as decimal strings — unitPrice, like "500.00" — in the invoice’s currency, which currencyCode sets once and defaults to EUR. Responses return them in minor units: millionths for invoice lines, hundredths elsewhere. VAT rates are integer percent, and an Idempotency-Key header is required whenever you issue.

curl https://descodify.pt/api/v1/customers \
  -H "Authorization: Bearer dsc_live_..." \
  -H "Content-Type: application/json" \
  -d '{"customerType":"business","name":"Acme Lda","country":"PT"}'

curl https://descodify.pt/api/v1/invoices \
  -H "Authorization: Bearer dsc_live_..." \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 6f2c6b6a-2f0e-4b0a-9c0a-000000000001" \
  -d '{
    "invoiceType": "invoice",
    "customerId": "<id from above>",
    "action": "issue",
    "items": [
      { "description": "Consulting", "quantity": 1, "unitPrice": "500.00", "vatRate": 23, "itemType": "services" }
    ]
  }'

The response is the issued invoice: sequential number, ATCUD, QR code data, and at_comm_status: "pending" while AT communication runs in the background. Full walkthrough, field-by-field, in the quickstart guide.

What's in the API

Customers, products and invoices with their full lifecycle, plus your issuer identity and the fiscal export file. Every response mirrors the same data model the app itself uses, so nothing is a stripped-down view.

Auth, scopes, and rate limits

Certified, not just connected

A lot of invoicing APIs built for other markets will happily hand you back a PDF that isn't a legally valid Portuguese invoice. Software that issues Portuguese invoices has to be AT-certified, assign sequential ATCUD codes, and report every issued document to the tax authority. The API is a thin layer over the exact same path Descodify's own app uses, not a workaround.

Every request, and everything it touches, stays on infrastructure hosted in the EU (Germany).

Reference and terms

The full OpenAPI 3.1 document is public, no key required, at /api/v1/openapi.json. Browse it interactively on the API reference page, or read the quickstart guide for a worked example of every step. Using the API is covered by the same Terms of Service as the rest of the product.

AI clients (MCP)

Descodify also speaks the Model Context Protocol. Point your AI assistant at @descodify/mcp, an open-source server, and it can issue certified invoices, create customers, and manage products in plain language, over the same certified path as the REST API and the app itself.

MCP is an open protocol, not ours. The same server runs unmodified in Claude Desktop, Claude Code, Gemini CLI, Cursor, Windsurf, VS Code's Copilot agent mode, Cline, and Zed. Use whichever AI client you already have.

{
  "mcpServers": {
    "descodify": {
      "command": "npx",
      "args": ["-y", "@descodify/mcp"],
      "env": { "DESCODIFY_API_KEY": "dsc_live_..." }
    }
  }
}

claude mcp add descodify \
  --env DESCODIFY_API_KEY=dsc_live_... \
  -- npx -y @descodify/mcp

{
  "mcpServers": {
    "descodify": {
      "command": "npx",
      "args": ["-y", "@descodify/mcp"],
      "env": { "DESCODIFY_API_KEY": "dsc_live_..." }
    }
  }
}

{
  "mcpServers": {
    "descodify": {
      "command": "npx",
      "args": ["-y", "@descodify/mcp"],
      "env": { "DESCODIFY_API_KEY": "dsc_live_..." }
    }
  }
}

Every client above defaults to https://descodify.pt. Set DESCODIFY_BASE_URL if you're pointing at a self-hosted or dev instance.

Pair the server with the public descodify skill on skills.sh. It teaches an agent the safe flow: read your business profile before building an invoice, confirm the line items and totals with you before issuing, and correct a mistake with a credit note rather than an edit, whether it's calling through the MCP server or the raw API directly.

Issuing stays irreversible either way: a real sequential number, communicated to the AT, correctable only by credit note. The server generates a fresh idempotency key on every issue, so a dropped connection and a retry from your AI can't mint the same invoice twice.

Source is MIT-licensed and public at github.com/descodify/mcp. The full OpenAPI document above covers every call it wraps.