Location events

event: location is already on the live stream. It is a Find My observation, not a maps-link pin in a bubble (those still arrive as event: message with a maps URL in text).

conversationId is the handle's DM, never a group. Coordinates on /v1 are numbers.

event: location
data: {"conversationId":"a0000000-0000-4000-8000-000000000001","occurredAt":"2026-08-24T18:07:00.000Z","from":"+14155550100","event":"location_update","latitude":40.76203,"longitude":-73.985918}

The frame

Cadence is Apple's. A share started from the Find My app, rather than from the Messages thread, may never write a bubble; the live observation is still this event when the Mac can see the share.

Pull, not only push

The latest observation per participant in a DM is also a synchronous read:

GET /v1/conversations/{conversationId}/location

See GET /v1/conversations/:id/location. After a drop, includeLocations: true on POST /v1/replay returns the same latest-per-participant set for that conversation. includeLocations without conversationId is 400.

Related