Get all contact requests
Retrieve directory contact-request history, including deleted partners and matchmaking assignments. Newest first unless a supported sort is supplied (oldest first with stale=true); ties are broken by id.
Authentication
Your API key, sent as Authorization: Token <your API key>
Path parameters
Query parameters
Inclusive creation start date (ISO 8601).
Inclusive creation end date (ISO 8601); midnight includes the entire day.
Only requests that were delivered to a partner: leaves out held requests and requests closed while held, as the requests report does.
Comma-separated project statuses to keep: new, contacted, engaged, on_hold, secured, launched_deployed, lost, or not_set for contact requests with no project status, an empty one, or a stored value that is not one of the listed statuses.
Exact routing source label to keep; repeat the parameter to keep several labels. An empty value keeps contact requests with no routing source.
Sort by created, company_name, entry_title or directory_name; prefix with - for descending. Omitted or unsupported: newest first (oldest first with stale=true). Ties are broken by id, so pages are stable.
Contact origin: contact_request or matchmaking. Omit to include both.
Exact contact-request state: pending, accepted or declined.
Response
new- Newcontacted- Contactedengaged- Engagedon_hold- On holdsecured- Securedlaunched_deployed- Launched / Deployedlost- Lost
matchmaking- Matchmakingcontact_request- Contact Request
same_message- Same message already sent to 2 partners todaysame_phone- Same phone number already sent to 2 partners todaysame_company- Same company already sent to 2 partners today