Delete an alert contact Beta
DELETE /api/v1/alerting/contacts/{id}
Delete a contact and all of its addresses.
Needs an X-API-Key header whose owner has permission to manage uptime monitors in the app. The call counts once against your daily quota. See Monitoring API: getting started for authentication, rate limits and errors.
The contact is also removed from every monitor and every team that used it. Alerts already in the history are kept.
Request
Response
200 · application/json
- { "id": "ct_5b8d1f0a9c2e4d6f7a83", "deleted": true, "usage": { "used": 46, "dailyLimit": 100, "tier": "free" } }
Errors
| Status | When |
|---|---|
401 | The API key is missing or invalid. |
403 | The key's owner doesn't have permission to change alert contacts, or the key isn't linked to a workspace. |
404 | No contact with that id in your workspace, including one already deleted. |
405 | The endpoint doesn't accept that method. |
429 | A rate limit or your daily quota was hit. Read Retry-After, in seconds. Writes are also limited to 30 a minute per key. |
500, 503 | Something went wrong, or the API is temporarily unavailable. Try again. |
Errors are JSON: { "error": "message" }. See Monitoring API errors.
Related
- Delete several contacts: in one call
- Update a contact: keep it, with fewer addresses