Skip to main content

Changelog

2026-04-17 — Brand casing on provider field​

Changed​

  • The provider field in all public-API responses (both /v1/* and /v2/* — /v1/lookup, /v1/invoices/send, /v2/invoices/send, artefact list, etc.) now emits "InvoStaq" instead of "Invostaq" to match the product's brand casing.
  • No request shape changes. No endpoint removals. No other field names or types changed.

Who needs to act​

  • Case-insensitive or display/log consumers: no action required.
  • Strict-equality consumers (x.provider === "Invostaq"): update to === "InvoStaq" or switch to case-insensitive comparison. The field is informational — we recommend treating it as a display string rather than a semantic flag.

v1.0.0 — Initial Release​

  • GET /v1/lookup — Peppol participant directory lookup
  • POST /v1/invoices/send — Send invoices through the Peppol network
  • Idempotency support via Idempotency-Key header
  • Webhook events: transaction.sent, transaction.failed, transaction.received
  • Sandbox (sk_test_) and production (sk_live_) environments
  • RFC 7807 error responses with extended fields for validation and network errors

Future releases will be documented here. Subscribe to release notifications in the Invostaq dashboard.