Oman's e-invoicing dates are now set in law: 1 April and 1 October 2027. Read our guide. Read the guide

For software vendors

Add Oman e-invoicing to your product

Your customers need PINT-OM e-invoices before their 2027 deadlines. Instead of building validation and document handling yourself, integrate with a documented, versioned API.

  • OpenAPI 3.1 and Postman
  • Organisation-scoped API keys
API request flowYour application authenticates with an organisation-scoped API key, submits a document, receives validation results and polls or reads its lifecycle status.Your applicationInvoice And TaxOpenAPI 3.1API key (scoped)POST documentValidation resultLifecycle statusAPI request flowYour application authenticates with an organisation-scoped API key, submits a document, receives validation results and polls or reads its lifecycle status.Your applicationInvoice And TaxAPI key (scoped)POST documentValidation resultLifecycle statusOpenAPI 3.1

How can a software vendor add Oman e-invoicing to its product?

Integrate with the Invoice And Tax REST API: authenticate with an organisation-scoped API key, submit documents, receive validation results and read each document's lifecycle status. The API is versioned under /api/v1/ and documented with an OpenAPI 3.1 specification, a Postman collection and a quick-start guide.

Developer funnel

A developer experience you can plan around

  • Versioned REST API

    Endpoints live under /api/v1/, so your integration is not broken by unannounced changes.

    API overview: Versioned REST API
  • OpenAPI 3.1 specification

    Generate clients in your language of choice and validate requests against the published contract.

  • Postman collection and quick start

    Make your first authenticated call from a ready-made collection and a step-by-step guide.

  • Scoped API keys

    Bearer keys are shown once and scoped to an organisation or branch, so each customer's access is contained.

  • Validation you do not have to build

    Versioned business rules and Schematron conformance checks return explained errors your users can act on.

  • Lifecycle status

    Read each document's status as it moves from validation to issue, and surface it in your own interface.

How we work with vendors

From sandbox conversation to customer roll-out

  1. 01

    Discovery

    Tell us about your product, your customers and the document types they issue.

  2. 02

    Technical walkthrough

    We review the API, authentication model and status flow with your developers.

  3. 03

    Integration build

    Your team builds against the specification with support from ours.

  4. 04

    Customer roll-out

    Agree onboarding, support routing and commercial terms for your customers.

Software-vendor enquiry

Tell us about your product

Which product do you build, which systems do your customers run, and roughly how many organisations would use e-invoicing?

Fields marked * are required.

We reply to this address only.

What kind of integration are you considering?

Up to 3,000 characters.

Start with the API overview

Review the endpoints and authentication model, then talk to us about your integration.

(opens in a new tab)