Zinevu
API reference

Offer items

An offer item is one rule: it decides when a line appears on an offer, what it says and what it costs.

Each item can carry an article_number — its code in your accounting or ERP, such as the Internal Reference of an Odoo article. That number is copied onto every offer line the rule writes, which is what lets an invoice be built from an offer without a mapping table in between.

GET/offer-items

prices:read

Your offer items and the article number each has.

Parameters
active_only
boolean
Leave out to see retired ones too.
has_article_number
boolean
Only items that carry one — the set worth syncing to an ERP.
updated_since
ISO 8601
Only records changed at or after this instant.
limit
integer, 1–100
Defaults to 25.
cursor
string
From meta.next_cursor.
Request
curl "https://api.zinevu.com/api/public/v1/offer-items?has_article_number=1" \  -H "Authorization: Bearer $ZINEVU_API_KEY"
Response
{  "data": [    {      "id": 1341,      "name": "Solarmodule",      "article_number": "vk-solar-01",      "kind": "product",      "vat_rate": 0,      "is_active": true,      "sort_order": 12,      "created_at": "2026-06-02T09:31:00+00:00",      "updated_at": "2026-09-05T14:10:22+00:00"    }  ]}

GET/offer-items/{article_number}

prices:read

One item, by the number your ERP holds.

Request
curl https://api.zinevu.com/api/public/v1/offer-items/vk-1001 \  -H "Authorization: Bearer $ZINEVU_API_KEY"

Article numbers#

Unique within the account, stored lowercase, and made of letters, digits, dots, dashes and underscores — so it is always safe in a path. The lookup lowercases what you send, so case does not matter.

The number on a line is a copy

Every line of an offer names the item that wrote it and that item's article number. The number is written onto the line at the moment the line is created, so an offer keeps its articles when an item is later renumbered or deleted. A line somebody typed by hand has neither.