One contact, with the supplier it belongs to
One contact: name, email, phone, city, country, description, role, department, preferred contact method, and the supplier it belongs to by id and name, with is_primary_contact saying whether it is that supplier's main contact.
contact_id is a whole number. A value that is not one is refused 400 before the database is touched, and one no contact has is refused 404.
A contact belongs to at most one supplier here: where a person is on several, this serves the first. supplier_id and supplier_name are null for a contact attached to no supplier.
Scope: suppliers:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/contacts/{contact_id}
- Auth: HTTP bearer
Path parameters
The contact's id, a whole number, as list_contacts 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 contact as it stands, with its supplier named.
Changes
No recorded changes to this operation across all 1 revision of this API.