One supplier's five scorecard figures
Five figures for one supplier, as an array: average_lead_time in days, total_pos_cost, every purchase order placed with them, in the organisation's currency, and the otif_score, on_time_score and in_full_score rates. Each carries key, unit, info and value.
Read the key, never the position: the order is stable today and is not part of the contract.
A value of null with info "Not enough delivery data" means the rate exists but too few delivery lines have been scored to publish it, and on-time carries its own reason for the same case. A null is therefore "not measured yet", never zero.
The same three rates are plain fields on get_supplier_details, which is the door when the address, the contacts or the lanes are wanted in the same call.
Scope: suppliers:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/inventory/suppliers/{supplier_id}/overview
- 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
Five cards, each {key, unit, info, value}. A null value is a figure not measured yet, and info says why.
Changes
No recorded changes to this operation across all 1 revision of this API.