Genesys Cloud - Developer Community!

Hi guys ,

Would like to ask for guidance regarding a VOICE agentless outbound campaign callback use case and the deprecation of the endpoint:
POST /api/v2/outbound/campaigns/{campaignId}/callback/schedule.

We have a VOICE agentless campaign, and inside the IVR flow there is a path where the customer can request a callback in order to be contacted again by the campaign at a future time/date.

The current deprecated endpoint fits this use case because it allows scheduling callbacks directly against the outbound campaign context.

However, the proposed alternative endpoints:

• /api/v2/conversations/{conversationId}/participants/{participantId}/callbacks
• /api/v2/conversations/callbacks

do not cover our use case properly.

The main blocker is that the proposed callback APIs require queue-based routing logic and mandatory queueId/name usage.

In our architecture, this information does not exist because:

• the campaigns are fully agentless,
• there is no ACD queue involved,
• and agentless campaigns do not provide/require queueId association.

Because of this, the proposed migration path does not appear compatible with VOICE agentless outbound campaign callback scheduling.

Any guidance, architectural recommendation, or alternative approach for handling this use case would be highly appreciated.

Thank you in advance for your time and help.

Markos