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.
Vendor API v1 — supplier integration docs
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.
What is Linra Omni
Section titled “What is Linra Omni”Linra Omni is one platform, built to carry more than one product line — not a separate stack per product. Scent (perfume and fragrance) is the first product line live on it today, and more will follow over time, each sitting on the same platform layer: the same auth model, the same response envelope, the same pagination and error contract. The moment a second product line ships, this same account and this same credential model extend to cover it — you don’t re-onboard.
This site documents the vendor-facing supply side of that platform: how you, as a supplier, submit offers, keep your cost and stock current, fulfil the orders assigned to you, and handle returns — today for Scent, end to end, with the platform layer already shaped to carry whatever comes next.
Who this is for
Section titled “Who this is for”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.
The credential model, in brief
Section titled “The credential model, in brief”Every vendor credential is capability-scoped — Offers, Stock, Cost, Orders, and
Account are each independently grantable, and a token only lets you do what it was actually
issued to do. Your first credential is always issued by a Linra admin as part of onboarding;
after that, you self-service further credentials yourself, but self-service can only match or
narrow the capabilities you already hold — never widen them. See
Vendor onboarding & credentials for the full flow, and
Authentication & capabilities for how a token actually gets used.
What you can supply today (Scent)
Section titled “What you can supply today (Scent)”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 & fulfilment
Poll the fulfilment groups assigned to you — packing/shipping details only, never partner money or identity — push Shipped/Delivered/Cancelled status updates, and handle your side of a return (propose an inspection outcome; Linra decides).
Webhooks
Get pushed order-assignment and offer-review-decision events instead of polling — with HMAC-signed, replay-resistant delivery.
A quick orientation
Section titled “A quick orientation”Every endpoint in this document lives on the dedicated vendor Gateway
(api-omni-vendors.linra.net) — commercial routes (offers, stock, orders, webhooks) under
/api/v1/scent, everything else (auth, profile, credentials) directly under /api/v1. All of it
requires a bearer token from POST /api/v1/auth/token. The Getting started
guide walks through credential exchange to your first authenticated call.
This is the vendor-facing surface only. Your own credentials are self-service (Account
capability); everything else — admin functionality, and any reselling-partner data (identity,
order totals, commission, VAT) — is permanently out of scope for this API. Both the guides and the
API Reference are split into a Platform layer (auth, profile, credentials — the
same shape regardless of which products you supply) and a Scent layer (this product’s own
endpoints and states) — see Platform overview and
URL conventions for the full framing.
Where to go next
Section titled “Where to go next”- New here? Start with Getting started, then the Integration journey for the full onboarding-to-fulfilled-order path.
- Not sure how you get your first credential at all? Read Vendor onboarding & credentials.
- Fulfilling Scent orders? Read Scent fulfilment for vendors.
- Want the full contract — auth, capabilities, every endpoint, status vocabularies, SLAs? Read the Vendor Integration Standard.
- Wiring up push notifications? Read Webhooks & HMAC verification — it has a worked, verified signature-verification code sample.
- Just need the wire shapes? Jump straight to the API Reference.