Storno.ro API

Storno.ro is an e-invoicing platform that integrates with e-invoice provider systems across the EU (Romania, Germany, Italy, Poland, France). This API allows you to manage companies, create and send invoices, track payments, and automate your invoicing workflow.

Base URL

https://api.storno.ro

Key Features

  • Multi-Country E-Invoicing — Integration with e-invoice provider systems (ANAF, XRechnung, SDI, KSeF, Factur-X)
  • Multi-Company Support — Manage multiple companies under one organization
  • Full Invoice Lifecycle — Create, issue, submit to provider, track payments
  • Document Types — Invoices, proforma invoices, credit notes, delivery notes, receipts (bonuri fiscale)
  • Recurring Invoices — Schedule automatic invoice generation
  • PDF & XML Generation — Generate UBL-compliant XML and professional PDFs with customizable templates
  • Multi-Language PDFs — Generate documents in Romanian, English, German, or French
  • Real-time Updates — WebSocket support via Centrifugo

LLMs

Machine-readable documentation files for AI assistants and LLMs:

  • llms.txt — Lightweight index with links and descriptions
  • llms-full.txt — Full content of all documentation pages

Integrations

  • CLI / MCP Server — Manage invoices through AI assistants (Claude, Cursor, Windsurf)
  • Stripe App — Create e-Facturi automatically from Stripe payments
  • Mobile App — iOS and Android app for invoicing on the go

Contributing

Authentication

All API requests require a Bearer token in the Authorization header. Most endpoints also require an X-Company header to specify the company context.

curl https://api.storno.ro/api/v1/invoices \
  -H "Authorization: Bearer {token}" \
  -H "X-Company: {company_uuid}"

See Authentication for details on obtaining tokens.

API Conventions

  • All requests and responses use JSON (Content-Type: application/json)
  • UUIDs are used as resource identifiers
  • Dates use ISO 8601 format (YYYY-MM-DD)
  • Timestamps use ISO 8601 with timezone (YYYY-MM-DDTHH:mm:ssZ)
  • Monetary amounts are numeric (not string-encoded)
  • Pagination uses page and limit query parameters
  • List responses include total, page, limit, and pages metadata
  • Soft-deleted resources are excluded from list endpoints by default

HTTP Methods

MethodUsage
GETRetrieve resources
POSTCreate resources or trigger actions
PUTFull resource update
PATCHPartial resource update
DELETEDelete resources

Rate Limiting

API requests are subject to rate limiting. Authentication endpoints have stricter limits to prevent abuse. See the Rate Limiting guide for full details on limits per endpoint.

Versioning

The API is versioned via the URL path. The current version is v1:

/api/v1/invoices