Summary
The legacy Workforce Management (WFM) Shift Trades APIs are being deprecated. Replacement APIs are already available as part of the modernized Shift Trades API framework introduced.
Migration guidance, including endpoint mappings and implementation examples, is available in the Shift Trading API Migration Guide:
https://developer.genesys.cloud/workforcemanagement/flexibility/shift-trading-api-migration
Effective Date
Monday, August 24, 2026
Details
The legacy Shift Trades APIs are being replaced by a modernized set of APIs that leverage a new shift trading service architecture. The updated architecture provides:
- Simplified maintainability
- Support for future Shift Trades capabilities and enhancements
Deprecating the legacy endpoints allows Genesys Cloud to consolidate on a single API model and continue delivering new functionality without maintaining duplicate implementations.
Customer Impact
Customers currently using the legacy WFM Shift Trades APIs must migrate to the replacement APIs before the legacy endpoints are removed.
This is a breaking change for affected customers. Integrations, applications, scripts, and workflows that continue to use the deprecated endpoints will cease to function after the retirement date.
Migration involves more than updating endpoint URLs. Customers must review and update their implementations to accommodate changes in:
- Request and response structures
- Endpoint behavior
- Processing patterns
A significant change in the replacement APIs is the adoption of a job-based asynchronous processing model.
While many requests may appear to complete synchronously during testing or under normal operating conditions, integrations must be designed to correctly handle asynchronous responses (HTTP 202 Accepted) and retrieve results through the documented job-completion workflow.
Customers should not assume requests will always complete synchronously.
Failure to implement asynchronous handling may result in integrations working during initial testing but failing or behaving unexpectedly when requests are processed asynchronously in production.
Customers are strongly encouraged to review and implement the guidance provided in the Shift Trading API Migration Guide, regardless of the behavior observed during development or early adoption.
Impacted Resources
Deprecated APIs
Replacement APIs
- GET /api/v2/workforcemanagement/managementunits/{managementUnitId}/weeks/{weekId}/shifttrades
- GET /api/v2/workforcemanagement/managementunits/{managementUnitId}/weeks/{weekId}/shifttrades?evaluateMatches=true
- POST /api/v2/workforcemanagement/managementunits/{managementUnitId}/weeks/{weekId}/shifttrades/state/bulk
- GET /api/v2/workforcemanagement/managementunits/{managementUnitId}/shifttrades/matched
- GET /api/v2/workforcemanagement/managementunits/{managementUnitId}/agents/{agentId}/shifttrades
- POST /api/v2/workforcemanagement/managementunits/{managementUnitId}/weeks/{weekId}/shifttrades
- PATCH /api/v2/workforcemanagement/managementunits/{managementUnitId}/weeks/{weekId}/shifttrades/{tradeId}
- POST /api/v2/workforcemanagement/managementunits/{managementUnitId}/weeks/{weekId}/shifttrades/search
- POST /api/v2/workforcemanagement/managementunits/{managementUnitId}/weeks/{weekId}/shifttrades/{tradeId}/match
- GET /api/v2/workforcemanagement/shifttrades
- GET /api/v2/workforcemanagement/managementunits/{managementUnitId}/shifttrades/users
Issue References
Contacts
@Andy Boland 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.