Skip to content
Request a demo Log in
Language: العربية

Mezan API

Build on top of your ledger

A public REST API reaching the same data the interface does: customers, products, invoices, journals. With an OpenAPI document, an SDK, and webhooks that tell your system what happened as it happens.

  • REST + JSON
  • OpenAPI
  • Webhooks
Talk to our team Documentation

What you get

  • Public REST API

    Read, create and update across Mezan’s core resources.

  • OpenAPI document

    A formal description you can generate a client from.

  • Webhooks

    Events pushed to you instead of a polling loop.

  • Keys and permissions

    A key operates within the organisation’s permissions, never above them.

  • Bulk create

    Bulk endpoints for migration and first-time imports.

Host

https://apiv2.mezan.sa

Style
REST
Format
JSON
Described by
OpenAPI
Events
Webhooks

A JSON API over HTTPS, authenticated per organisation.

The resources you can reach

The same resources the interface works on, under the same accounting rules. An invoice created through the API posts its journal entry and follows the e-invoicing flow exactly as one created by hand does.

Sales

  • Customers
  • Quotations
  • Sales invoices
  • Receipts
  • Credit notes

Purchasing

  • Vendors
  • Purchase orders
  • Purchase invoices
  • Payments
  • Debit notes

Products and stock

  • Products and categories
  • Stores
  • Quantities and movements
  • Units of measure
  • Serial numbers

Accounting

  • Chart of accounts
  • Manual journals
  • Reporting dimensions
  • Balances
  • Tax types

From nothing to a first request

Four steps, none of which needs a call with sales.

  1. 1

    Enable API access

    API and webhook access is included from the advanced plans up. The pricing page lists what your plan covers.

  2. 2

    Create a key

    Keys are created inside the organisation and inherit its permissions. A key never grants what its creator does not hold.

  3. 3

    Read the description

    The OpenAPI document describes the resources and fields, and generates a client in your language rather than you writing one.

  4. 4

    Subscribe to events

    Register an endpoint and receive an event on every change you care about, instead of polling.

Webhooks

Stop polling every minute

Polling is expensive, slow, and wrong in between cycles. Register an endpoint and the event arrives when it happens, so your system stays consistent with Mezan without a lag.

  • Events delivered to your endpoint as changes occur
  • Well suited to keeping stock and balances in step with other systems
  • Event replay is available on the store integrations
  • Same API, same permission model

Common uses

  • Stock sync

    With a sales channel or an external warehouse.

  • Dashboards

    Feed internal dashboards with live figures.

  • Internal systems

    Wire Mezan into your own operations stack.

Looking to connect a Salla or Zid store? That is already built and needs no code — see the integrations page.

Integrations page

The rest of the platform

The API is one of eight products running on top of Mezan Core.

Common questions

Is the API available on every plan?

API and webhook access is included from the advanced plans up, and high-volume limits sit with the enterprise plan. The pricing page has the detail.

Does the API bypass accounting rules?

No. A document created through the API goes through the same rules: the journal entry posts, stock moves, and the e-invoicing flow applies exactly as it would from the interface.

What is the authentication model?

A key created at organisation level that operates within that organisation’s permissions, so a key never carries authority its creator does not have.

Is there an SDK?

Yes, alongside the OpenAPI document, which can generate a client in your language directly.

Book a demo

Leave your details and we’ll call you back within one business day to arrange your session.

We use your details only to contact you about your Mezan session.