← all problem types

contact_already_confirmed

409 Conflict   This contact is already confirmed.

When you get it

This contact is already confirmed. 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:

contactId

The contact this problem is about.

confirmedAt

When the contact was confirmed.

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/contact-already-confirmed",
  "title":  "This contact is already confirmed.",
  "status": 409,
  "code":   "contact_already_confirmed",
  "errors": [
    { "contactId": …, "confirmedAt": … }
  ]
}