Summary
The /mobiledevices APIs are being deprecated as part of ongoing platform modernization.
Customers should migrate to the supported Web Messaging APIs, which provide equivalent device management capabilities.
Effective Date
Wednesday, September 30, 2026
Details
The /mobiledevices APIs are backed by legacy functionality that has been superseded by the Web Messaging platform. Device management has been migrated to newer services, and the legacy APIs are no longer actively used.
Consolidating on the Web Messaging APIs reduces platform complexity and ensures customers use the current, supported interfaces for push device management.
Customer Impact
No customer impact is expected based on current API usage.
Customers who are still using the deprecated /mobiledevices APIs must migrate to the supported Web Messaging APIs before the removal date.
The primary replacement endpoint is:
POST /api/v2/webmessaging/deployments/{deploymentId}/pushdevices/{tokenId}
Customer Action Required
Customers should:
- Identify any integrations or applications using the deprecated /mobiledevices APIs.
- Update those integrations to use the supported Web Messaging API
Impacted Resources
The following APIs are being deprecated and will be removed:
- GET /api/v2/mobiledevices — Get a list of all devices
- POST /api/v2/mobiledevices — Create a device
- GET /api/v2/mobiledevices/{deviceId} — Get a device
- PUT /api/v2/mobiledevices/{deviceId} — Update a device
- DELETE /api/v2/mobiledevices/{deviceId} — Delete a device
Replacement API
- POST /api/v2/webmessaging/deployments/{deploymentId}/pushdevices/{tokenId}
Issue References
PLUS-1892
PLUS-2514
Contacts
@Anna Janica Please reply to this announcement with any questions. This helps the wider developer community benefit from the discussion. We encourage you to use this thread before contacting the designated person directly. Thank you for your understanding.