Get an alert contact Beta
GET /api/v1/alerting/contacts/{id}
One alert contact, with every address it can be reached on.
Needs an X-API-Key header whose owner has access to uptime monitoring in the app. The call counts once against your daily quota. See Monitoring API: getting started for authentication, rate limits and errors.
Path parameters
| Name | Type | Description |
|---|---|---|
id required | string | The contact id, for example ct_5b8d1f0a9c2e4d6f7a83. |
Request
Response
200 · application/json
- {
- "contact": {
- "id": "ct_5b8d1f0a9c2e4d6f7a83",
- "name": "Night shift",
- "methods": [
- { "id": "318", "kind": "email", "target": "[email protected]", "severity": "all", "optedOut": false },
- { "id": "319", "kind": "email", "target": "[email protected]", "severity": "high", "optedOut": false }
- ],
- "createdAt": "2026-09-17T09:02:11.000Z",
- "updatedAt": "2026-09-17T09:02:11.000Z"
- },
- "usage": { "used": 44, "dailyLimit": 100, "tier": "free" }
- }
See the contact object for every field.
Errors
| Status | When |
|---|---|
401 | The API key is missing or invalid. |
403 | The key's owner doesn't have access to uptime monitoring, or the key isn't linked to a workspace. |
404 | No contact with that id in your workspace. |
405 | The endpoint doesn't accept that method. |
429 | A rate limit or your daily quota was hit. Read Retry-After, in seconds. |
500, 503 | Something went wrong, or the API is temporarily unavailable. Try again. |
Errors are JSON: { "error": "message" }. See Monitoring API errors.
Related
- Update a contact: change it
- List contacts: find the id