The brand's contacts at one account, and the email domains that make a thread theirs
The brand's contacts at one account and the email domains that make a thread theirs: the account's name, its recorded domains, and one entry per contact with name, email, phone, role, department, contact type, last interaction date and whether they are the main contact.
Both in one read because they answer one question, which is how this account is reached.
domains null is not an account without domains: it means nobody has recorded one, which domains_reason says, and until one is recorded no inbound thread can be matched to this account at all. Recording a domain is a write on this prefix and is not public.
Sold with Essentials+: without Tightly Connect the answer is 403 plan_excludes.
Scope: accounts:read.
Request
- Base URL: https://api.app.tightly.io
- URL: https://api.app.tightly.io/api/v1/wholesale/retailers/{partner_id}/contacts
- Auth: HTTP bearer
Path parameters
The account. An id, never a name. Duplicate account names are ordinary in apparel.
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 account, its recorded email domains (or null with the reason there are none), and every contact with role, department, type and when we last heard from them.
Changes
No recorded changes to this operation across all 1 revision of this API.