Remove a member
Remove one member from a list.
Removes one member from a list. The company or person itself is not deleted. On a monitored customer or prospect list, removing a member stops its monitoring through that list.
Smart lists are managed in the app; their members can't be added or removed through the API.
Route
DELETE
/api/v3/lists/{kind}/{list_id}/members/{member_id}
Access modes
Use a workspace API key. The workspace is inferred from the key.
Authorization: Bearer sk_live_...Path parameters
| Parameter | Type | Description |
|---|---|---|
| kind | string | company or profile. It matches the kind of the list. |
| list_id | integer | ID of the list. |
| member_id | integer | ID of the member, as returned by List members. |
Example request
curl -X DELETE "https://api.getsillage.com/api/v3/lists/company/12/members/301" \
-H "Authorization: Bearer $SILLAGE_API_KEY"Success response
Status: 200 OK
{
"data": {
"id": 301,
"deleted": true
}
}Response fields
| Field | Type | Description |
|---|---|---|
| data.id | integer | ID of the member that was removed. |
| data.deleted | boolean | Always true. |
Errors
| Status | Meaning |
|---|---|
| 401 | The API key is missing or invalid. |
| 404 | The list does not exist, or the member is not on it. |
| 409 | The list is a smart list. Smart lists are managed in the app; their members can't be added or removed through the API. |
| 422 | kind, list_id or member_id is not valid: detail is "Invalid URL parameters" and errors names the parameter. |
| 429 | Rate limit exceeded. |
| 500 | An unexpected server error occurred. |
Error responses use RFC 9457 problem documents with Content-Type: application/problem+json. type is always about:blank; code tells one problem from another, detail says what went wrong this time, and errors names the field at fault.