L Linet Developers
Home / Journeys / Running service calls
Journey 08 · Service calls

Running service calls from your system

With the Service module, a company tracks service calls (קריאות שירות): a customer reports a fault on a machine, a technician is assigned, the work and the parts are recorded, and the call is closed. Through API v2 your system can open calls, follow them and record the work, and hear about every change by webhook.

Module routes. Every route here answers only while the company has the Service module; otherwise 404 module_inactive. Scopes service:read and service:write.

The records

RecordIsRoutes
service callthe call: customer, machine, status, type, technician, the fault and the work done/service-calls
instrumenta machine the call covers, by line/service-calls/{id}/instruments
linea part or a charge, in a document line's names (unit_price, line_total_with_vat…)/service-calls/{id}/lines
timetime logged, in its time type's unit/service-calls/{id}/time
machinea customer's equipment, with its counter readings/machines, /machines/{id}/counters
listsstatuses (and each one's SMS template), types, time types, counters, conditions/service-calls/statuses…, read-only

Opening a call

POST /service-calls with at least the customer, the type and the status:

{
  "customer_id": 376, "type_id": 1, "status_id": 1,
  "machine_id": 55, "description": "Printer jams on every page",
  "start_time": "2026-11-02T09:30:00"
}

Two fields work only here, as on the screen: fast_item adds a machine as the first instrument, and auto_items adds that many new machines for the customer, numbered from the company's serial prefix.

Following it

  • Change it with PATCH /service-calls/{id}; only the fields sent change.
  • Record the work: add lines (picking item_id brings the item's name, unit, price and currency), instruments and time. Lines and instruments are changed and removed by their line number; time is added, not changed.
  • The customer's SMS: moving a call to a status that has an SMS template texts the customer, exactly as the screen does, when the company sends status SMS. The template is written as in Mail and SMS templates.
  • Documents (quote, delivery note, invoice) are made on the screen for now. A call's documents gives the ids of the ones it got.

Closing it

A closed call is read_only. Writing it, or its lines, instruments or time, answers 409, unless the company turns on API: allow changing a closed service call in its service settings. There is no DELETE: a call is closed, not deleted.

Webhooks

Gold and above, as every webhook (Receiving webhook notifications):

EventWhen
service_call.createda call is opened
service_call.updateda call changes, or any of its instruments, lines or time. The payload is the whole call with them, as GET /service-calls/{id} answers it; one event per save, however many lines it touched
machine.created / machine.updateda machine is added or changed

They are offered only to a company with the Service module.

The reference

Every route, field and answer: API v2 › Service calls, Machines.