One supplier whole
One supplier, whole: identity and address, currency, minimum order value, payment terms in days, the resolved lead time and its source, every contact with the primary one named separately, the email domains that route this supplier's mail, the OTIF, on-time and in-full rates, and two views of its warehouses.
location_lead_times is one entry per active warehouse carrying the RESOLVED lead time, the supplier × warehouse override if one is set, else the organisation default, with source saying which answered. lanes is the same warehouses stated whole: the lane's own override (lead_time null means no override), the container it names, what the ladder resolved to, basis naming the rung that answered (lane, supplier, organisation, or null for no container on file), the forwarder's quote per container in cents, and the inland leg's road limit in kg. Both lists come out of one statement, so they cannot disagree about a warehouse.
payment_terms_days null means nobody has recorded terms, which is read as no lag rather than as zero. container_type_id on the supplier is the middle rung: null means "use the organisation default", which is not the same as no container.
An id this organisation does not have is refused 404. get_supplier_overview is the door when only the five scorecard figures are wanted.
Scope: suppliers:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/inventory/suppliers/{supplier_id}
- Auth: HTTP bearer
Path parameters
The supplier's id, as list_suppliers serves it.
Headers
The date train to answer on. One train exists today, 2026-11, the one this reference describes and the one every key is minted on, so the call answers on it with or without this header. Send it anyway, so a client built now names its train from the start.
Response
The supplier's record: terms, contacts, domains, the delivery rates, and the warehouses as both resolved lead times and whole lanes.
Changes
No recorded changes to this operation across all 1 revision of this API.