Skip to content

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 per-endpoint API reference on docs.invora.app.

Get started ZATCA compliance API reference ↗

Start here

  •  Quickstart

    From zero to a frozen, authority-submitted document in a handful of calls.

    Quickstart

  •  Getting started

    Base URLs, environments, and your first authenticated request.

    Getting started

  •  Authentication

    OIDC tokens, scopes, and machine-to-machine access.

    Authentication

Explore by area

  •  Invoicing

    Issue invoices, credit notes, and debit notes through one ergonomic surface — draft to frozen, with the QR code and authority submission generated on freeze.

    Invoicing

  •  Billing

    Plans, subscriptions, metered usage, wallets, and automated invoicing with Invora Billing.

    Billing

  •  Collect payments with Tap

    Connect Tap Payments, generate payment links for invoices, handle saved cards, and react to payment webhooks.

    Tap payments

  •  Identity & tenancy

    Registration, onboarding, and connected businesses for platform and reseller models.

    Identity

  •  gRPC-JSON transcoding

    How the REST/JSON surface maps to the gRPC services — camelCase fields, JSON bodies.

    Transcoding

  •  Webhooks

    Real-time billing event delivery: signature verification, retries, and delivery guarantees.

    Webhooks

  •  ZATCA compliance

    Saudi e-invoicing (ZATCA Phase 2): onboarding, clearance, and reporting.

    ZATCA integration

  •  Marketplace invoicing

    The intermediary-platform invoicing study for marketplaces and aggregators.

    Marketplace invoicing

  •  API conventions

    List and filtering, field masks, entity versioning, and 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.