Try the RankNibbler SEO API

Update an alert contact Beta

PATCH /api/v1/alerting/contacts/{id}

Change a contact's name, its addresses, or both. Send only what you want to change. PUT does the same thing.

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.

Body

FieldTypeDescription
name optionalstringA new name, up to 120 characters. Leave it out to keep the current one.
methods optionalobject[]Replaces the whole list of addresses. Same shape and rules as create.

Request

Response

200 · application/json
  1. {
  2. "contact": {
  3. "id": "ct_5b8d1f0a9c2e4d6f7a83",
  4. "name": "Night shift (EMEA)",
  5. "methods": [
  6. { "id": "318", "kind": "email", "target": "[email protected]", "severity": "high", "optedOut": false }
  7. ],
  8. "createdAt": "2026-09-17T09:02:11.000Z",
  9. "updatedAt": "2026-09-17T11:24:03.000Z"
  10. },
  11. "usage": { "used": 45, "dailyLimit": 100, "tier": "free" }
  12. }

Errors

StatusWhen
400An empty name, no address left, an address that isn't a valid email, or an invalid severity or kind.
401The API key is missing or invalid.
403The key's owner doesn't have permission to change alert contacts, or the key isn't linked to a workspace.
404No contact with that id in your workspace.
405The endpoint doesn't accept that method.
429A rate limit or your daily quota was hit. Read Retry-After, in seconds. Writes are also limited to 30 a minute per key.
500, 503Something went wrong, or the API is temporarily unavailable. Try again.

Errors are JSON: { "error": "message" }. See Monitoring API errors.

Related