Register

The iOS app starts the Live Activity and registers the push token directly with Live Hive. Your backend does not need a token-forwarding endpoint. Tokens rotate; the iOS SDK calls this again whenever ActivityKit issues a new one.

POST /v1/activities/register
Authorization: Bearer lh_pub_...

{
  "activity_id": "customer-activity-123",
  "push_token": "...",
  "type": "delivery"
}

type and expires_at are optional. Same project + activity_id replaces the stored token instead of inserting a duplicate. The response includes the activity ID and basic metadata. It never includes the push token or APNs credentials.

Prefer the iOS SDK, which does this for you:

LiveHive.configure(publicKey: "lh_pub_...")
LiveHive.register(activity)

A secret lh_live_ key can still create activities at POST /v1/activities. That is a legacy path. Do not use it in new integrations. Public keys cannot call it, and they cannot update or end activities. See iOS SDK.