Invora Guides

Integration and compliance guides for the Invora e-invoicing and billing platform. How to model a flow, which approach fits, and what the regulation requires — paired with the generated API reference on docs.invora.app.

Get started ZATCA compliance API reference ↗

Start here

•  Quickstart

  ---

  From zero to a frozen, authority-submitted document.

  Quickstart

•  Authentication

  ---

  OIDC tokens and machine-to-machine access.

  Authentication

•  gRPC-JSON transcoding

  ---

  How the REST/JSON surface maps to the gRPC services.

  Transcoding

Explore by area

•  Invoicing

  ---

  Invoice lifecycle (draft → frozen → cleared/reported) and the invoicing API.

  Invoicing

•  Billing

  ---

  Plans, subscriptions, metered usage, and automated invoicing.

  Billing

•  Identity & tenancy

  ---

  Onboarding, connected businesses, and multi-tenancy.

  Identity

•  Admin & webhooks

  ---

  Admin APIs and real-time event delivery.

  Admin & webhooks

•  ZATCA & marketplace

  ---

  Saudi e-invoicing integration and the intermediary-platform invoicing study.

  Compliance

•  API conventions

  ---

  List/filter, field masks, entity versioning, error handling.

  Conventions

Guides vs. the API reference

These guides explain how and why. For the exhaustive, always-current per-endpoint request/response schemas, use docs.invora.app — it is generated from the protos on every change, so it is the source of truth for wire formats. Whenever a guide names an endpoint, its canonical shape lives there.