Skip to content

Get Association

This endpoint returns one project-to-contact association. You identify it by the project ID in the path and the contact ID in the query string.

GET /v1/associations/associations/:id

Include your API key in the x-api-key header. See Authentication.

associations:read
ParameterTypeRequiredDescription
idstringYesProject ID.
ParameterTypeRequiredDescription
contactIdstringYesContact ID paired with the project ID.

This endpoint does not accept a request body.

Terminal window
curl "https://api.crewsum.com/v1/associations/associations/project-mno123pqr4567890?contactId=contact-jkl123mno4567890" \
-H "x-api-key: $CREWSUM_API_KEY"

On success, the API returns HTTP 200 OK.

{
"message": "Successfully fetched association",
"data": {
"association": {
"projectId": "project-mno123pqr4567890",
"projectName": "Project Name",
"contactId": "contact-jkl123mno4567890",
"contactName": "Contact Name",
"contactType": "MANAGER",
"notificationLevel": "COPY_ONLY",
"projectEndCustomer": "End Customer Name"
}
}
}
  • This endpoint can return an association that was removed when its project or contact was deleted. The response does not show that the association is removed. To list only active associations, use List Associations.
  • projectEndCustomer is the name of the project’s end customer, or null.
StatusMeaning
400The request did not include contactId. The message is contactId must be supplied.
404No association was found for the supplied project and contact IDs.
500Crewsum could not fetch the association. The message is Error fetching association.

Authentication and scope failures are described in Errors.

This endpoint does not trigger a webhook.