Update a contact request's project status
Moves a contact request in your directory to a new project status. projectStatus is required: new, contacted, engaged, on_hold, secured, launched_deployed or lost. Setting lost also requires lostReason; send lostReasonDetail (up to 500 characters) only when the reason is other. A closed request’s status can’t change. Each change sends a contact_request_updated webhook event.
Authentication
AuthorizationToken
Your API key, sent as Authorization: Token <your API key>
Path parameters
contactId
ID of the contact request to update
Request
This endpoint expects an object.
projectStatus
new- Newcontacted- Contactedengaged- Engagedon_hold- On holdsecured- Securedlaunched_deployed- Launched / Deployedlost- Lost
lostReason
customer_went_unresponsive- Customer went unresponsivelost_to_another_provider- Lost to another providerbudget_or_timing- Budget or timingnot_a_fit_after_discovery- Not a fit after discoverycustomer_handled_in_house- Customer handled in houseother- Other
lostReasonDetail
Response
Updated contact request
firstName
lastName
email
companyName
href
id
created
state
projectStatus
new- Newcontacted- Contactedengaged- Engagedon_hold- On holdsecured- Securedlaunched_deployed- Launched / Deployedlost- Lost
entry
directory
source
matchmaking- Matchmakingcontact_request- Contact Request
Allowed values:
matchOrigin
customForm
events
firstViewedAt
phone
companyWebsite
comments
utmQueryParams
customFormResponseId
declineReason
declineReasonDetail
closeReason
closeReasonDetail
routingSource
isStale
daysWaiting
reminderCount
holdReason
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
Allowed values:
reminder
senderBlocked
closeNotificationRecipients
delivery
Errors
400
Bad Request Error
403
Forbidden Error
404
Not Found Error
429
Too Many Requests Error