Genesys Cloud – Deprecation: Legacy workforce management shift trades APIs

Genesys is deprecating the legacy workforce management (WFM) shift trades Application Programming Interface (APIs) as part of ongoing improvements to Shift Trades functionality in Genesys Cloud.

Genesys is replacing the legacy shift trades APIs with a modernized set of shift trades APIs that are already available for customer use. The new APIs support existing functionality while enabling:

• Improved scalability and performance.
• More robust and reliable operations.
• Support for new and enhanced shift trade features in future releases.

These changes allow Genesys to continue evolving the platform and improving the overall customer experience.

Genesys will mark the existing shift trades endpoints as deprecated and remove them after 24 August, 2026. The replacement APIs provide equivalent functionality but use a new architecture and a job-based asynchronous execution model. Customers currently using the legacy APIs must migrate to the new shift trades APIs before the removal date.

What is being deprecated?

Genesys is deprecating the legacy WFM Shift Trades APIs, including endpoints that support used for:

• Querying trades
• Evaluating trades
• Creating and updating trades
• Matching trades
• Bulk and per-trade state updates
• Trade summaries and agent-specific queries

These endpoints are typically management unit–scoped and use synchronous processing.

What replaces this functionality?

The modern Shift Trades APIs replace all deprecated endpoints. Key characteristics of the replacement APIs include:

• Job-based (asynchronous) processing.
• POST-based operations, including queries.
• Business unit–based routing with management unit filtering in the request body.
• Updated request and response structures, including nested response objects.
• Dedicated endpoints for specific operations.

Detailed migration guidance, including endpoint mapping and examples, will be available.

Am I affected?

You are affected if you:

• Use any legacy WFM Shift Trades API endpoints.
• Have built custom integrations, applications, or workflows that depend on these endpoints.

Genesys is identifying impacted customers and partners through telemetry and may contact affected organizations directly.

What do I need to do before the removal date?

To avoid disruption, migrate to the new Shift Trades APIs as soon as possible.

Migrating to the new APIs may require more than updating endpoints. You may also need to:

• Replace GET requests with POST requests for query operations.
• Move parameters from URL paths or query strings into the request body.
• Update request payload structures.
• Update response parsing to support nested response objects.
• Handle job-based responses, including HTTP 200, 201, and 202 responses.

Genesys will provide detailed migration documentation, including examples and endpoint mappings.

Need help?

Genesys will provide a dedicated migration guide that includes:

• Endpoint mapping
• Request and response examples
• Required code changes
• Migration best practices

For additional assistance, contact My Support.