Who owns the request

A request opened over the API still has to appear in front of someone at your organisation. Havnly decides that from adjuster_email.

Send adjuster_email

{
  "loss_address": "1200 Pine St",
  "adjuster_email": "dana@carrier.example",
  "adjuster_name": "Dana Reyes"
}

If that address belongs to an adjuster or claims manager on Havnly, then:

• the request is assigned to them;
• it appears in their team’s list, not just their own, because it takes their carrier workspace;
• they are notified that it arrived;
• everything that follows — a home matched, a lease signed, a booking cancelled — reaches them rather than nobody.

The response tells you whether the address was recognised, so a typo does not go unnoticed for a fortnight:

{
  "data": {
    "claim_ref": "REQ-4A91C2",
    "assigned_adjuster_user_id": "77c1…",
    "adjuster_email_matched": true
  }
}

adjuster_email_matched: false means the request was created and is live, but nobody at your organisation owns it yet. Invite the person to Havnly, then assign it.

Handing a request over

POST /claims/{reference}/assign

{
  "adjuster_email": "sam@carrier.example",
  "adjuster_name": "Sam Okafor"
}

Use it when the person who opened the request goes on leave, or a complex placement moves to someone senior. The new owner is notified and picks up every later notification. 409 no_such_adjuster means that address is not an adjuster on Havnly — invite them first.

Requires the claims:write scope.

If you send no adjuster at all

Some integrations post requests from a system, not a person. Ask Havnly to point your organisation at a carrier workspace once; after that every request you create lands in that team’s list even with no adjuster_email, and anyone on the team can pick it up.

Without either, a request is still created and still matched — Havnly’s coordinators work it — but your own staff will not see it in their portal.