Contacts due a follow-up
Surface contacts who have gone quiet — a logged touch exists, but the most recent one predates `inactive_days` (default 30) ago and no open task is already tracking the follow-up. Ordered most-recently-quiet first (the timely nudges). Detection is a plain inactivity query — no model call. With `include_never_contacted`, contacts with no logged touch at all, added before the cutoff, come back as `never_contacted`. `type` keeps one kind of contact in both lists.
Surface contacts who have gone quiet — a logged touch exists, but the most recent one predates inactive_days (default 30) ago and no open task is already tracking the follow-up. Ordered most-recently-quiet first (the timely nudges). Detection is a plain inactivity query — no model call. With include_never_contacted, contacts with no logged touch at all, added before the cutoff, come back as never_contacted. type keeps one kind of contact in both lists.
Authorization
bearerAuth contacts:readA gallery API key, sent as Authorization: Bearer gpk_… (or the x-api-key header).
In: header
Scope: contacts:read
Query Parameters
Only contacts with no interaction for at least this many days.
7 <= value <= 36530Page size. Defaults to 20; the maximum is 100.
1 <= value <= 5020Also list contacts with no logged touch at all, added before the cutoff and with no open task, as never_contacted.
Keep only contacts of this type, in both lists.
Value in
- "collector"
- "institution"
- "consignor"
- "lender"
- "advisor"
- "press"
- "curator"
- "artist"
- "other"
Response Body
application/json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
application/problem+json
{ "data": [ { "contact_id": "string", "name": "string", "contact_type": "collector", "company": "string", "lead_status": "new", "last_interaction_at": "string", "days_since_last_interaction": -9007199254740991, "last_interaction_summary": "string" } ], "inactive_days": -9007199254740991, "never_contacted": [ { "contact_id": "string", "name": "string", "contact_type": "collector", "company": "string", "lead_status": "new", "created_at": "string" } ]}{ "type": "../dictionary", "title": "string", "status": 0, "detail": "string", "code": "invalid_request", "retry": "permanent", "details": null}{ "type": "../dictionary", "title": "string", "status": 0, "detail": "string", "code": "invalid_request", "retry": "permanent", "details": null}{ "type": "../dictionary", "title": "string", "status": 0, "detail": "string", "code": "invalid_request", "retry": "permanent", "details": null}{ "type": "../dictionary", "title": "string", "status": 0, "detail": "string", "code": "invalid_request", "retry": "permanent", "details": null}{ "type": "../dictionary", "title": "string", "status": 0, "detail": "string", "code": "invalid_request", "retry": "permanent", "details": null}{ "type": "../dictionary", "title": "string", "status": 0, "detail": "string", "code": "invalid_request", "retry": "permanent", "details": null}Export a contact's full record GET
Returns one contact's complete record — profile, interactions, tasks, notes, pipeline memberships, ownership links, offer history, and memory — as structured JSON for GDPR data-portability (Art. 20).
Get a contact GET
Returns the contact plus its recent interactions, open tasks, pipeline memberships, ownership links, and — for a first-party editor — its private notes. The id of a contact merged into another returns the contact it merged into.