Linra Omni Vendor Integrations
Overview
Linra Omni Vendor API v1
Section titled “Linra Omni Vendor API v1”The Linra Omni vendor-facing API — reachable through the dedicated vendor Gateway’s /api/v1
facade (src/ApiGateway/Linra.Omni.VendorGateway/appsettings.json, ReverseProxy:Routes, the
vendor-*-v1-route family). Every path in this document is a real, currently-deployed
vendor-reachable route; this document is GENERATED — see tools/openapi-spec-gen/ and do not
hand-edit vendor-openapi.json.
Workstream W (Vendor Platform), W-01 gave vendors their own Gateway process/domain (separate from
the partner-facing Gateway); W-02 moved every commercial route under a product segment
(/scent) and dropped the redundant /vendor segment entirely — the whole Gateway IS the vendor
plane, so repeating that in every path added nothing. W-02 also added the two product-neutral
self-service groups below (Profile, Credentials), hosted directly in Identity rather than proxied
through a product service.
This is a SEPARATE property from the Linra Omni partner developer docs
(developers.linra.net / src/DeveloperPortal/) — a vendor is a supplier Linra sources
product from, not a reselling partner, and the two audiences must never see each other’s
surface (00-decisions.md §V, Point V-3). This document deliberately excludes every
partner-facing endpoint, every internal/admin surface, and every partner-money/commission/
identity field a fulfilling vendor has no need to see.
The Vendor Integration Standard, getting-started, and guides
Authentication
Section titled “Authentication”vendorBearer
Section titled “vendorBearer”A vendor access token from POST /api/v1/auth/token (audience vendor-api, 5-minute lifetime, capability-scoped).
Security scheme type: http
Bearer format: JWT