Try the RankNibbler SEO API

Create an alert team Beta

POST /api/v1/alerting/teams

Put people in a named group, so a monitor can alert "Support" rather than eight 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.

Body

FieldTypeDescription
name requiredstringThe team name. Up to 120 characters.
userIds optionalinteger[]Ids of people in your workspace, up to 200.
contactIds optionalstring[]Ids of your alert contacts, up to 200.

Request

Response

201 Created with the team.

201 · application/json
  1. {
  2. "team": {
  3. "id": "tm_2c7e91a4b6d0f3e85a17",
  4. "name": "Support",
  5. "userIds": [42, 57],
  6. "users": [
  7. { "id": 42, "name": "Sam Taylor", "email": "[email protected]" },
  8. { "id": 57, "name": "Ada Okoro", "email": "[email protected]" }
  9. ],
  10. "contactIds": ["ct_5b8d1f0a9c2e4d6f7a83"],
  11. "contacts": [{ "id": "ct_5b8d1f0a9c2e4d6f7a83", "name": "Night shift" }],
  12. "createdAt": "2026-09-17T09:10:40.000Z",
  13. "updatedAt": "2026-09-17T09:10:40.000Z"
  14. },
  15. "usage": { "used": 49, "dailyLimit": 100, "tier": "free" }
  16. }

Errors

StatusWhen
400No name, nobody in the team, or an unknown contact id.
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.
405The endpoint doesn't accept that method.
409The workspace already has 50 teams.
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