Thank you for the detailed assessment and for flagging the endpoints of concern.
For most endpoints in this announcement, the initial RPM values are fixed in the service for this first rollout, so we are not able to raise them per organization without a broader platform change. The published 150 RPM for PATCH /api/v2/users/{userId}/queues therefore remains the current limit for now. We will continue to monitor usage and revisit as we move toward outer-limits, where per-organization adjustments are more flexible.
Original Message:
Sent: 08-07-2026 03:06
From: Yusuke Managi
Subject: Rate Limiting on Assignment Service Public APIs
Hello Raghavendra,
Thank you for the information.
Could you please confirm the planned production implementation date for these API rate limits? As we are already well into the 60-day notice period, we would like to understand when the limits are expected to be enabled in production.
Also, could you please confirm whether the initial rate limits listed in your post are still current, or if there have been any changes since they were published?
Based on our current assessment, we expect that the following endpoints may exceed the proposed limits:
PATCH /api/v2/users/{userId}/queuesGET /api/v2/routing/wrapupcodes
Would it be possible to increase the limits for these endpoints as follows?
PATCH /api/v2/users/{userId}/queues: 200 RPMGET /api/v2/routing/wrapupcodes: 150 RPM
We would appreciate your review and feedback.
Thank you.
------------------------------
Yusuke Managi
------------------------------
Original Message:
Sent: 07-10-2026 07:29
From: Raghavendra Kopalle
Subject: Rate Limiting on Assignment Service Public APIs
Good morning,
Thank you for your questions on the Rate Limiting on Assignment Service Public APIs announcement.
Below are the initial per-organization limits (requests per minute, RPM) for the endpoints listed in the announcement. The table includes both internal assignment-service paths and the corresponding public Platform API paths.
These limits were set using observed traffic plus headroom for a first release. We will monitor usage after enablement and revisit limits if needed.
Initial RPM limits
Queue
Method | assignment-service (internal) | Public API (Developer Center) | Initial limit (RPM per org) |
PUT | /v2/organizations/{orgId}/queues/bulk | No direct public Platform API path (internal platform use only) | 50 |
POST | /v2/organizations/{orgId}/queues | POST /api/v2/routing/queues | 180 |
PUT | /v2/organizations/{orgId}/queues/{queueId} | PUT /api/v2/routing/queues/{queueId} | 360 |
Agent
Method | assignment-service (internal) | Public API (Developer Center) | Initial limit (RPM per org) |
PUT | /v2/organizations/{orgId}/agents/{agentId}/queues | PATCH /api/v2/users/{userId}/queues | 150 |
PUT | /v2/organizations/{orgId}/agents/{agentId}/queues/{queueId} | PATCH /api/v2/users/{userId}/queues/{queueId} | 150 |
PUT | /v2/organizations/{orgId}/agents/{agentId}/status | PUT /api/v2/users/{userId}/routingstatus | 300 |
Wrap-up codes
Method | assignment-service (internal) | Public API (Developer Center) | Initial limit (RPM per org) |
GET | /organizations/{orgId}/wrapupCodes | GET /api/v2/routing/wrapupcodes | Outer-limits (platform default 100 RPM; tier 200 RPM where applicable) |
Queue members
Method | assignment-service (internal) | Public API (Developer Center) | Initial limit (RPM per org) |
GET | /v2/organizations/{orgId}/queues/{queueId}/users | GET /api/v2/routing/queues/{queueId}/members | 20,000 |
POST | /v2/organizations/{orgId}/queues/{queueId}/users | POST /api/v2/routing/queues/{queueId}/members | 3,000 |
PUT | /v2/organizations/{orgId}/queues/{queueId}/users | PATCH /api/v2/routing/queues/{queueId}/members | 150 |
PUT | /v2/organizations/{orgId}/queues/{queueId}/users/{memberId} | PATCH /api/v2/routing/queues/{queueId}/members/{memberId} | 150 |
DELETE | /v2/organizations/{orgId}/queues/{queueId}/users/{memberId} | DELETE /api/v2/routing/queues/{queueId}/members/{memberId} | 150 |
Conversation
Method | assignment-service (internal) | Public API (Developer Center) | Initial limit (RPM per org) |
PATCH | /v2/organizations/{orgId}/conversations/{conversationId} | PATCH /api/v2/routing/conversations/{conversationId} | 10,500 |
POST | /v2/organizations/{orgId}/conversations/{conversationId}/assign | POST /api/v2/conversations/{conversationId}/assign | 750 |
Rollout
We are currently in the 60-day notice period for this change on public Platform API routes. Limits will be rolled out incrementally by environment; production enablement for customer-facing use will align with that notice period.
These are initial limits. We will monitor traffic and throttling (HTTP 429) after enablement and adjust limits based on observed usage where appropriate.
Limit increases / integration concerns
If you believe a critical integration may exceed these limits, please contact us with the organization ID(s), endpoint(s), and expected traffic (RPM). We will review during the rollout period and discuss options if needed.
Please let us know if you need any additional information.
Regards,
------------------------------
Raghavendra Kopalle
Director, Architecture
------------------------------
Original Message:
Sent: 07-09-2026 07:21
From: Laura Cepeda
Subject: Rate Limiting on Assignment Service Public APIs
Good morning,
Could you please specify which are those limits for each one of the internal endpoints? What will be the rate limit (requests per minute) per organization for each of the affected endpoints? Additionally, for rollout and validation conditions, what is the deployment schedule by environment (Dev/Test/Production), and will we be able to validate behavior before activation in production?
Related to exceptions or limit increases: If necessary, is it possible to request an increase in limits or a temporary exception for critical integrations?
Thank you very much.
Regards!
Laura.
------------------------------
Laura Cepeda
------------------------------
Original Message:
Sent: 07-07-2026 10:56
From: Raghavendra Kopalle
Subject: Rate Limiting on Assignment Service Public APIs
Thank you for your question.
The Impacted Resources section lists internal assignment-service paths (how the service is implemented). Those paths do not appear in the Developer Center. Customer and partner integrations use the public Platform API paths below.
Please use the Public API column when assessing whether this change affects your customers.
Queue
assignment-service (internal) | Public API (Developer Center) |
PUT /v2/organizations/{orgId}/queues/bulk | No direct public Platform API path (internal platform use only) |
POST /v2/organizations/{orgId}/queues | POST /api/v2/routing/queues |
PUT /v2/organizations/{orgId}/queues/{queueId} | PUT /api/v2/routing/queues/{queueId} |
Agent
assignment-service (internal) | Public API (Developer Center) |
PUT /v2/organizations/{orgId}/agents/{agentId}/queues | PATCH /api/v2/users/{userId}/queues |
PUT /v2/organizations/{orgId}/agents/{agentId}/queues/{queueId} | PATCH /api/v2/users/{userId}/queues/{queueId} |
PUT /v2/organizations/{orgId}/agents/{agentId}/status | PUT /api/v2/users/{userId}/routingstatus |
Wrap-up codes
assignment-service (internal) | Public API (Developer Center) |
GET /organizations/{orgId}/wrapupCodes | GET /api/v2/routing/wrapupcodes |
Queue members
assignment-service (internal) | Public API (Developer Center) |
GET /v2/organizations/{orgId}/queues/{queueId}/users | GET /api/v2/routing/queues/{queueId}/members |
POST /v2/organizations/{orgId}/queues/{queueId}/users | POST /api/v2/routing/queues/{queueId}/members |
PUT /v2/organizations/{orgId}/queues/{queueId}/users | PATCH /api/v2/routing/queues/{queueId}/members |
PUT /v2/organizations/{orgId}/queues/{queueId}/users/{memberId} | PATCH /api/v2/routing/queues/{queueId}/members/{memberId} |
DELETE /v2/organizations/{orgId}/queues/{queueId}/users/{memberId} | DELETE /api/v2/routing/queues/{queueId}/members/{memberId} |
Conversation
assignment-service (internal) | Public API (Developer Center) |
PATCH /v2/organizations/{orgId}/conversations/{conversationId} | PATCH /api/v2/routing/conversations/{conversationId} |
POST /v2/organizations/{orgId}/conversations/{conversationId}/assign | POST /api/v2/conversations/{conversationId}/assign |
Please let me know if you need any additional information.
Note: I may not receive notifications for replies in this thread. For follow-up, please email me at kumar.kopalle@genesys.com
Regards,
Kumar
------------------------------
Raghavendra Kopalle
Director, Architecture
------------------------------
Original Message:
Sent: 06-26-2026 03:53
From: 健一 小林
Subject: Rate Limiting on Assignment Service Public APIs
Hi,
As shown in the attachment, none of the APIs listed under "Impacted Resources" are included.
------------------------------
Kobayashi, Kenichi
------------------------------