L Linet Developers
Linet API Docs · v2.0.0

Build with Linet without reading the source twice.

Documents, items, accounts, payments, and Israeli tax‑authority certification — one JSON API. This portal pairs the full reference with guided journeys for the integrations people actually build first.

Every request needs three HTTP headers: login-id, login-hash, and login-company. These identify you and the Linet company (tenant) you're operating on. They're issued by Linet when your integration is set up — see the company & setup journey if you're wondering where a company comes from in the first place.
Five journeys to start with
Catalog

Create & update an item

Add a new item to the catalog, search for it by SKU before touching it again, then apply a partial update — the safe read‑before‑write pattern for every catalog sync.

Start journey
Documents

Create a document

Issue an invoice, receipt, or invoice‑receipt: how doctype, line items (docDet) and payment lines (docCheq) fit together, with real payloads for cash, cheque, credit card and bank transfer.

Start journey
Setup

New company & initial config

Where login-company comes from: how a Linet company is provisioned, what gets configured on day one, and what to hand your integration once it's ready.

Start journey
Tax Authority

Tax Authority Allocation Number tax certification

Authorize against the Israeli Tax Authority's allocation‑number API, store the certificate, and get a confirmation number stamped onto a real document.

Start journey
Webhooks

Receiving SNS webhook notifications

The payload shape Linet publishes to AWS SNS when an Item, Item Category, Account or Document changes — envelope fields, changedAttributes, and real example notifications.

Start journey