Skip to main content

​
Concurrent Live Activities Limits

iOS supports up to 5 concurrent Live Activities per app on a device. The exact capacity is dynamic: iOS may allow fewer depending on device conditions and other active or scheduled Live Activities. ActivitySmith mirrors this iOS limit server-side. This gives API clients a clear, actionable response instead of allowing APNs to accept a start that iOS may not create on the device. Paid accounts receive a 429 response when a targeted device has reached the enforced concurrency threshold. During a trial, starting a sixth Live Activity ends the oldest active Live Activity before starting the new one. Limit responses always include the highest active count among targeted devices. When multiple targeted devices have mixed capacity, the response also includes blocked_devices and targeted_devices to explain which targets prevented the start. End Live Activities as soon as they are no longer useful so iOS can release their capacity.

​
API Rate Limits

Rate limits are measured in requests per minute and are primarily in place to prevent abuse. When configured correctly, your real bottleneck will be concurrent live activities. Shared account limit: 60 requests per minute across these endpoints:
  • POST /push-notification
  • PUT /live-activity/stream/{stream_key}
  • DELETE /live-activity/stream/{stream_key}
  • POST /metrics/{metric_key}/value
These rate limits are enforced to ensure fair usage and availability of the API for all users. If you require higher limits, please contact us at adam@activitysmith.com.