← all problem types

duplicate_monitor

409 Conflict   A monitor with this url and type already exists on this account.

When you get it

A monitor with this url and type already exists on this account. It is always answered with HTTP 409 - one code means one status, so a client may key its handling on either.

Fields it carries

Inside each errors[] entry, beside pointer:

existingId

The id of the resource that already holds the key you tried to claim.

key

The uniqueness key the request collided on.

A field is omitted when the server genuinely does not know it - an absent member is never the same as an empty one.

How to fix it

The request conflicts with the resource's current state. Re-read the resource and decide, rather than retrying blindly.

Shape

{
  "type":   "https://api2.host-tracker.com/problems/duplicate-monitor",
  "title":  "A monitor with this url and type already exists on this account.",
  "status": 409,
  "code":   "duplicate_monitor",
  "errors": [
    { "existingId": …, "key": … }
  ]
}