---
title: "Workday API Rate Limits When Many Employees Ask Questions…"
description: "What Workday publishes about REST, SOAP, RaaS, and WQL limits when many employees ask questions at once, and what it does not publish."
url: https://kiweely.com/guides/workday-rate-limits-when-employees-ask-in-chat
---

# Workday API Rate Limits When Many Employees Ask Questions in Chat

Workday throttles REST and RaaS with HTTP 429 when a tenant is overloaded, and SOAP can surface the same pressure as HTTP 500. Extract ceilings and EIB concurrency are different meters. No page fetched here prints one requests-per-second number for employee chat.

-   **Checked** against Workday on November 16
-   Applies to **Workday Extend**
-   5 min read
-   Published November 16
-   By Kiweely

Workday API Rate Limits When Many Employees Ask Questions in Chat

A company-wide assistant does not get its own Workday capacity. Every question becomes REST, WQL, SOAP, or a custom report on the same tenant that payroll and integrations already use. Workday publishes how it pushes back, and it publishes several ceilings that are easy to misread as a chat quota.

[Kiweely Bridge](https://kiweely.com/bridge) (coming next) bills unlimited calls at the company price. That sentence is about Kiweely’s invoice. It does not raise the tenant limits below.

## What happens when the tenant is busy

[Integrations, EIB, and Web Service Limits](https://developer.workday.com/documentation/dan1370797408285/ReferenceIntegrationsandWebServiceLimits) says Workday throttles, under high load:

-   Workday Web Services (SOAP)
-   Reports-as-a-Service
-   The REST API

When other requests overload tenant resources, Workday rejects calls with:

| API | Response the page names |
| --- | --- |
| REST and RaaS | 429 Too Many Requests |
| SOAP and RaaS | 500 Internal Service Error, which can mean too many requests |

Workday’s advice on that page is an exponential back-off and caching. It also says a burst of invalid requests can be rate-limited with 429 so one customer’s error spike does not exhaust shared resources. The opening note says Workday may throttle or suspend access until usage is back inside the limit, and that extra capacity, where Workday sells it, is a separate purchase.

This page does **not** print a single “N requests per second” figure for ordinary REST. Do not copy a number from a vendor’s blog into a design review. The entitlements screen inside a tenant is the place a customer sees their own allowance; this public reference is the behavior when the tenant is already overloaded.

## Ceilings that are not a chat quota

Same page, different meters. Quoting them without the label causes bad capacity plans.

**API extract requests** are RaaS extract interfaces only. The maximums are totals across those extract interfaces:

| Customer size on the page | Per 24 hours | Per 60 minutes |
| --- | --- | --- |
| Fewer than 3,500 workers | 75,000 | 15,000 |
| Fewer than 10,000 workers | 100,000 | 30,000 |
| Fewer than 100,000 workers | 250,000 | 75,000 |
| More than 100,000 workers | 350,000 | 100,000 |

An employee asking “what is my time-off balance?” is not, by itself, an extract. An integration that pulls a report every few minutes is. If the assistant is wired to a web-service-enabled custom report and someone asks for the whole population, you are much closer to report and response limits than to a chatty lookup.

**EIB concurrency** is up to 5 concurrent integrations if resources are available. Workday suggests avoiding the top of the hour. That limit is for EIBs, not for how many employees may open a chat.

**Other hard sizes** that still apply if a tool returns a large payload:

| Limit | Figure on the page |
| --- | --- |
| Web-service response instances | 1 million. Narrow with criteria, filters, or dates |
| RaaS advanced custom report enabled for web services | 2 GB |
| Incoming web-service request, other than import | 500 MB |
| Incoming import web-service request | 2 GB |
| HTTP header size | 16 KB |
| SOAP and REST attachment or image | 30 MB |
| Paged-request cache | 2 hours between paged requests, and 30 minutes after the last page. Page 1 builds the cache and should not use a tight timeout |

Workday does not log GET requests, unsuccessful requests, or web-service responses. A 429 storm can be invisible in the response log unless you send external integration HTTP headers for server-side tracking.

## WQL limits that change how a question should be asked

[WQL result limits](https://developer.workday.com/documentation/GUID-98ecf957-d369-4439-b541-ae8be7844401/ReferenceWQLResultLimits) say a query returns at most 1 million rows.

| Where you call | Timeout on that page |
| --- | --- |
| The tenanted host | 30 minutes |
| The Workday Cloud Platform API gateway (`api.workday.com`) | 5 minutes |

If the query would exceed 1 million rows and you set no LIMIT, it fails. A LIMIT of 1 million or less succeeds and returns at most 1 million rows. You view 10,000 rows at a time. `LIMIT` as a clause caps the total. `limit` as a parameter sets the page size. The keyword is not case-sensitive; Workday uses both forms.

[The WQL REST reference](https://developer.workday.com/documentation/GUID-5c940864-7651-4e28-a9d2-79b45292e66a-enHYPHENus/ReferenceWQLRESTAPI) adds the transport split: GET `/data` for a query under 2,048 characters, POST `/data` for a query from 2,048 to 16,000 characters. You only receive rows your security can see. Tenanted hosts use `https://{hostname}/api/wql/{version}/{tenant}`. The platform gateway uses `https://api.workday.com/wql/{version}`.

A headcount question that scans every worker, with no organization filter, is how a chat hits the row cap and the timeout. A question about the signed-in worker does not.

## How to plan the busy morning

Open enrollment, payday, and a manager cascade are the real tests. Workday’s published controls are tenant-wide. Practical consequences, without inventing a rate:

1.  Keep the default question small. The person’s own balances and elections are a different load from an unconstrained report.
2.  Cache reference data that does not change per employee, as Workday recommends, and back off on 429 and on SOAP 500 that is really load.
3.  Do not schedule a full-population extract at the same minute everyone is paid.
4.  Treat page 1 of a paged call as slow. Give it time to fill the cache.
5.  Separate “Kiweely does not meter calls” from “Workday will not throttle.” Bridge (coming next) is the first sentence. The limits page is the second.

A personal developer tenant is free for one person on Bridge and is the wrong place to learn a 5,000-person spike. Load still belongs on a non-production tenant that has production-like volume, and even there the limits page allows Workday to throttle.

## Frequently asked questions

### Will 1,000 employees chatting at once get 429?

Workday does not publish the concurrency number that would answer yes or no. It does say REST and RaaS return 429 when other requests overload the tenant, and SOAP can return 500 for the same reason. Plan for that response. Do not plan for an unpublished quota.

### Does unlimited Bridge pricing remove these limits?

No. Unlimited calls is the company invoice for Kiweely Bridge, which is coming next. The tenant limits in this guide still belong to Workday.

## Sources checked

-   [Integrations, EIB, and Web Service Limits](https://developer.workday.com/documentation/dan1370797408285/ReferenceIntegrationsandWebServiceLimits)
-   [Reference: WQL Result Limits](https://developer.workday.com/documentation/GUID-98ecf957-d369-4439-b541-ae8be7844401/ReferenceWQLResultLimits)
-   [Reference: WQL REST API](https://developer.workday.com/documentation/GUID-5c940864-7651-4e28-a9d2-79b45292e66a-enHYPHENus/ReferenceWQLRESTAPI)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### Separating Production and Sandbox Workday Endpoints So Demos Miss Live Workers Workday gives every tenant its own URL. Production holds live data. Sandbox and Sandbox Preview are typically copies of it. Implementation tenants and the sample-data demonstration tenant are the safer demo targets. A user-delegated connector follows whichever URL the person signs in on.](https://kiweely.com/guides/separate-production-and-sandbox-workday-endpoints)
-   [### Correlating Workday Audit Events with AI Assistant Tool Calls Workday’s agent audit separates the agent account from the person it acted for. Ordinary web-service reads are a weaker trail: Workday does not log GET or unsuccessful web-service requests. A user-delegated connector still acts as the worker, and its own telemetry omits names and pay.](https://kiweely.com/guides/correlating-workday-audit-with-ai-assistant-calls)

### More guides on Integrations and APIs

[All 89 guides](https://kiweely.com/guides#integrations)

-   [Workday SFTP File Contracts, PGP, and Overnight Failures](https://kiweely.com/guides/workday-sftp-file-contracts-pgp-overnight-failures)
-   [Recover Workday Integration Attributes After a Sandbox Refresh](https://kiweely.com/guides/workday-sandbox-refresh-integration-attributes)
-   [Inventory Every Workday Integration System, Schedule, and Owner](https://kiweely.com/guides/inventory-workday-integration-systems-schedules-owners)
-   [Sandbox Checklist Before AI Chat, Custom Screens, or Integration Platforms](https://kiweely.com/guides/sandbox-checklist-before-ai-chat-screens-or-integrations)
-   [Security Review Packet: Pass-Through UI, AI Chat, and Zero-Retention Integrations](https://kiweely.com/guides/security-review-packet-pass-through-ui-chat-and-integrations)
-   [What Is an EIB in Workday? How to Build, Template and Load One](https://kiweely.com/guides/what-is-an-eib-in-workday)
-   [How do you move an acquired company into the acquirer’s Workday tenant?](https://kiweely.com/guides/workday-move-acquired-company-into-acquirer-tenant)
-   [Who can launch a specific Workday integration, and what permissions does that user need?](https://kiweely.com/guides/workday-who-can-launch-integration)

### From the blog on Integrations and APIs

[All posts](https://kiweely.com/blog)

-   [How Workday’s Twice-Yearly Releases Break In-House MCP Servers and REST Integrations](https://kiweely.com/blog/how-workday-twice-yearly-releases-break-custom-mcp-servers)
-   [Turning Your Existing Workday RaaS Reports into Governed AI Tools](https://kiweely.com/blog/exposing-existing-workday-raas-reports-to-claude-and-chatgpt)
-   [Embedding Live Workday Time Off, Pay, and Approvals Inside DingTalk, Feishu, and Lark](https://kiweely.com/blog/embedding-workday-self-service-inside-dingtalk-feishu-lark)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
