Skip to content

Delete Supplier Contact

This endpoint soft-deletes a supplier contact. The record is marked as deleted but is not removed.

DELETE /v1/supplier-contacts/supplier-contacts/:id

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

supplier-contacts:write
ParameterTypeRequiredDescription
idstringYesSupplier contact ID.

This endpoint does not accept a request body.

Terminal window
curl -X DELETE "https://api.crewsum.com/v1/supplier-contacts/supplier-contacts/suppliercontact-vwx123yza4567890" \
-H "x-api-key: $CREWSUM_API_KEY"

On success, the API returns HTTP 200 OK.

The message currently says “supplier” instead of “supplier contact”. Do not match on the message text.

{
"message": "Successfully deleted supplier suppliercontact-vwx123yza4567890"
}
  • This is a soft delete. The API sets isDeleted to true and keeps the record.
  • Deleted contacts no longer appear in List Supplier Contacts. Get Supplier Contact still returns them, with "isDeleted": true.
  • The API cannot undo a delete.
  • An unknown ID still returns 200.
  • After the delete, Crewsum sends the supplier-contacts.deleted webhook event. The payload is { "contacts": [{ "supplier": <supplier>, "supplierContact": <contact> }] }, with "isDeleted": true on the contact. For an unknown ID, the event is still sent, with an empty contacts array.
StatusMeaning
400The ID path segment was empty (for example, a trailing slash). Message: TaskID not supplied.
500Crewsum could not delete the contact. Message: Error deleting supplier <id>.

Authentication and scope failures are described in Errors.