Skip to content

Linra Omni Vendor Docs

Submit offers, keep your stock and cost current, fulfil the orders assigned to you, and get pushed notifications — all behind one versioned, capability-scoped facade.

This site is for suppliers Linra sources product from — vendors. If you are a reselling partner integrating to place orders and sell through Linra Omni, you want a different site entirely: the Linra Omni Developer Docs. The two roles are distinct, unrelated identities with separate credentials, separate tokens, and separate APIs — a vendor credential never works against the partner API, and vice versa.

Offers

Submit and edit product offers — matched to an existing catalog item or as a free-form new entry — through the same review workflow the Linra catalog team already uses.

Cost & stock

Push wholesale cost changes (through the approval pipeline) and declared availability/quantity (applied instantly) — independently of each other and of the Offers capability.

Orders

Poll the fulfilment groups assigned to you — packing/shipping details only, never partner money or identity — and push Shipped/Delivered/Cancelled status updates.

Webhooks

Get pushed order-assignment and offer-review-decision events instead of polling — with HMAC-signed, replay-resistant delivery.

Every endpoint in this document lives under /api/v1/vendor on the Linra Omni Gateway. All of it requires a bearer token from POST /api/v1/vendor/auth/token, and every capability (Offers/Stock/Cost/Orders) is independently grantable on your credential — a token only lets you do what it was actually issued to do. The Getting started guide walks through credential exchange to your first authenticated call.

This is the vendor-facing surface only. There is no credential management, no admin functionality, and no reselling-partner data (identity, order totals, commission, VAT) anywhere in this document.