---
title: "Workday Orchestrate API limits, quota and usage — Kiweely"
description: "What Workday documents for rate limits and API usage in Orchestrate and Extend apps: 429 responses, Data Usage, retry policies and how to cut call counts."
url: https://kiweely.com/guides/workday-orchestrate-api-usage-limits-quota
---

# How are API calls from Workday Orchestrate and Extend apps limited and counted, and can I set my own rate limit?

Workday documents a per-second API limit that returns 429, plus a Data Usage entitlement for Extend apps in Production. The developer documentation we checked has no setting for a customer-defined rate limit or quota; you control volume with page size, batching and retry policies.

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

Workday documents two different controls on the API calls that Orchestrate and Extend apps make: a per-second limit on calls reaching your tenant, which answers with HTTP 429, and a Data Usage entitlement that measures successful API traffic from Extend apps in Production. The developer documentation we checked has no setting for a customer-defined rate limit or quota on an orchestration. Volume is under your control through how you page, batch and retry.

If you have seen a product announcement about user-defined rate limiting or quota management for Orchestrate, its settings are not described in the Developer Site documentation we checked, whose release notes run to 30 October 2026. This page covers what is documented. For the Monday-morning self-service case and the RaaS extract caps, see [designing for tenant concurrency and rate limits](https://kiweely.com/guides/workday-api-rate-limits-concurrency-workforce-self-service).

## What limits does Workday publish for API calls from Orchestrate and Extend apps?

| Control | What Workday says | Source |
| --- | --- | --- |
| Per-second tenant limit | Workday limits the number of API calls that can interact with your tenant per second. Over the limit you get a 429; calls complete again as soon as the rate drops below it. | Entitlements Dashboard |
| 429 on overload | REST and RaaS answer 429 when other requests overload tenant resources; SOAP and RaaS can answer 500, which can also be caused by too many requests. | Integrations, EIB, and Web Service Limits |
| Invalid-request guardrail | A process that generates an excessive volume of invalid requests is temporarily rate-limited with a 429. | Integrations, EIB, and Web Service Limits |
| RaaS extract volume | 15,000 per 60 minutes and 75,000 per 24 hours for fewer than 3,500 workers, rising to 100,000 and 350,000 above 100,000 workers. | Integrations, EIB, and Web Service Limits |
| Graph API | 429 when requests overload the tenant; page size default 20, maximum 100; request timeout 3 minutes. | Limits on Extend App Components |
| Synchronous calls through the gateway | Cannot exceed 5 minutes, except Graph API (3 minutes). | WCP API Gateway |

Workday states that when you reach or exceed any of these, it may throttle your use or suspend your access until usage is back within the limit.

## How is API usage by an Extend app counted?

The Entitlements dashboard of the Developer Site tracks Data Usage: the total volume in GB of all inbound and outbound data transfers for Extend apps in your Production environment. It counts all successful API requests and responses from your app to any Workday or third-party API. It does not count API responses that contain attachments. A request is successful when its response code is not in 400-499 or 500-599.

Two things follow from that definition. The measure is data volume, not the number of calls, so a few large responses cost more than many small ones. And an app that retries into a wall of errors adds load on the tenant’s per-second limit without adding to Data Usage.

The dashboard colours the figure: black below 85% of your entitlement, orange from 85% up to 100%, red at or above 100%. Integration Apps and External Home Page Cards orchestrations do not count towards the Extend Apps in Production entitlement.

## How do I see how many calls an app makes?

Three places on the Developer Site, all documented:

-   **Analytics dashboard, App Summary:** per app, the API Request Rate (requests per second), API Error Rate and Data Usage. App Metrics has an API tab with the performance of each API the app calls. Filter by environment such as Production or Sandbox.
-   **Logs tab:** Access and Remote logs show client requests and requests to external services. Workday deletes log files older than 30 days; an admin can download them first.
-   **Insights API:** `GET /reporting/v1.1/apps/{appId}/orchestrations/{orchName}/runs` returns runs with `computeDuration`, state and process IDs, and a run’s detail lists `stepsSuccessful` and `stepsFailed` per process. Event data is kept for 29 days, and the API documents that a 429 should be met with exponential back-off.

## Worked example: a loop that makes 400 calls and gets throttled

An orchestration reads a list of 400 workers and, inside a loop, sends one Send Workday API Request per worker to fetch a detail record. Loop iterations are processed in parallel unless something forces them to run in order, so many of the 400 calls can reach the tenant at the same time. Past the per-second limit, the extra calls come back 429.

Without a retry policy, an unsuccessful HTTP response does not fail the orchestration: Workday states that to make a failed response fail the run you must define a custom retry policy with a success range. So the run can finish while workers are missing, which is the pattern in [orchestrations that show success but some steps failed](https://kiweely.com/guides/orchestrate-errors).

The fix, in order of effect:

1.  **Fetch in pages.** Replace the per-worker loop with Send Paged Workday REST Call, whose properties are Limit, Offset, Max Pages and Flatten Result. REST `limit` defaults to 20 and accepts at most 100 (Workday REST API Pagination), so 400 workers is 4 calls at `limit=100` instead of 400.
2.  **Ask for less.** Filter at the source, so the call returns only the records the orchestration needs.
3.  **Add a retry policy.** In Orchestration Settings, open HTTP Retries and create one: a name, Maximum Total Retries (at most 60), a default backoff (Retry Interval in milliseconds, Increment Factor, Max Interval), and a Successful Response Code Range such as 200 to 299 so a final failure fails the run. Add a condition set with the Status Code 429 and, if you want Workday’s guidance followed, an Exponential Interval backoff. A Retry-After Header backoff is also available, with a Max Interval you accept.
4.  **Attach the policy** on the step’s Settings tab, in Retry Settings. It applies to Send HTTP Request, Send WWS Pagination API Request and Send Workday API Request.
5.  **Slow the loop only if you must.** Force Sequential Processing on the loop’s Early Stop Condition makes iterations run one after another, but Workday warns it can significantly increase processing time and cause a timeout that would not otherwise happen. See [looping, pagination and limits](https://kiweely.com/guides/workday-orchestrate-looping-pagination-limits) and [large loads inside the runtime limits](https://kiweely.com/guides/workday-orchestrate-runtime-limit-large-loads).

Result to look for after the change: in the Insights API, a run whose processes show `stepsFailed` of 0, and in the Analytics dashboard a lower API Request Rate for the app.

## What do I check to keep API usage down?

-   Page every list call and ask for the maximum page size the API allows.
-   Cache values that do not change within a run instead of fetching them in each loop iteration.
-   Do not retry 400-class responses; they are errors in the request, and a volume of them triggers the invalid-request guardrail.
-   Retry timeouts on reads freely; before re-sending a write, read the destination, because the request may have been accepted. See [HTTP retry and polling](https://kiweely.com/guides/workday-orchestrate-http-retry-polling).
-   Test at production volume in a non-production tenant before promotion, and read the Analytics dashboard’s API Request Rate for the app.
-   Check Entitlements before a bulk load in Production, so a load does not push Data Usage into the red band.

## Frequently asked questions

### Can I set a rate limit or quota on a Workday Orchestrate orchestration?

Not in anything Workday publishes in its developer documentation that we checked. What you can set is an HTTP retry policy (up to 60 retries, with backoff), the page size and Max Pages on paged calls, and whether a loop runs in parallel or sequentially. Workday sets the tenant-side limits itself.

### Do failed API calls count towards the Extend Data Usage entitlement?

No. Workday defines Data Usage as the volume of successful API requests and responses, and a request with a 400-499 or 500-599 response is not successful. Failed calls still count against the per-second limit, because that limit is on calls reaching the tenant.

### What does a 429 from Workday mean in an orchestration?

Too Many Requests. Workday rejects requests when other requests overload the tenant's resources, and also rate-limits a process that sends a high volume of invalid requests. Retry with exponential back-off and fewer parallel calls.

### Where do I see how many API calls my Extend app makes?

On the Developer Site Analytics dashboard: API Request Rate (requests per second) and API Error Rate per app, and Data Usage per app. The Entitlements dashboard shows total Data Usage against your contract.

## Sources checked

-   [Entitlements Dashboard](https://developer.workday.com/documentation/uxv1588614326668)
-   [Reference: Limits on Extend App Components](https://developer.workday.com/documentation/GUID-c58fce8e-198e-402e-9846-e1be8a429bad)
-   [Define HTTP Retry Policies](https://developer.workday.com/documentation/ymw1677347032713)
-   [Reference: Integrations, EIB, and Web Service Limits](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/it-administrator-resources/limitations-and-availability/dan1370797408285.html)
-   [Concept: Workday Cloud Platform API Gateway](https://developer.workday.com/documentation/GUID-6141e955-7cfe-4bee-b736-73a108d19d9f-enHYPHENus)
-   [Concept: Workday REST API Pagination](https://developer.workday.com/documentation/lvb1611857200890)
-   [Concept: Insights API](https://developer.workday.com/documentation/GUID-1d6a3cc0-0528-400b-9f20-c6150420838f)

## Related guides

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

-   [### Designing for Workday Tenant API Concurrency and Rate Limits During Peak Employee Traffic Workday protects shared tenant resources dynamically rather than publishing a fixed per-second REST quota: overloaded tenants return HTTP 429 (REST/RaaS), HTTP 503 (server timeout S27), or HTTP 500 (SOAP/RaaS), while RaaS extracts cap hourly and daily calls by worker count.](https://kiweely.com/guides/workday-api-rate-limits-concurrency-workforce-self-service)
-   [### How to keep large Workday Orchestrate loads inside the runtime limits: templates, checkpoints, batches and child runs First find the limit you hit: 25 seconds for a page call, 5 minutes synchronous, 60 minutes per process (45 before production), or 200 MB in memory. Then use an Integration System or async template, add checkpointing steps, batch writes and split work into child integrations.](https://kiweely.com/guides/workday-orchestrate-runtime-limit-large-loads)
-   [### HTTP retry policies and polling in Workday Orchestrate: how they work and how to configure them Retry policies and polling are set in Settings and chosen on the HTTP step. A policy allows up to 60 retries with backoff and defines success; without a success range, a failed response does not fail the run. Polling waits on an external job up to 48 hours, never on Workday APIs.](https://kiweely.com/guides/workday-orchestrate-http-retry-polling)
-   [### Workday Orchestrate Looping, Pagination, and Batching Over Large Datasets Configure Send Paged Workday REST Call, Send Paged Workday SOAP Call, Send Paged HTTP Request, Loop, Batch Loop, and Join Loop components in Workday Orchestrate without exceeding runtime, process, or memory limits.](https://kiweely.com/guides/workday-orchestrate-looping-pagination-limits)

### More guides on Orchestrate

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

-   [Keep in Studio, Move to Orchestrate, or Call Studio from Orchestrate—With AI in the Loop](https://kiweely.com/guides/studio-orchestrate-trigger-integration-with-ai-in-loop)
-   [AI Triage Evidence Pack: Keep Studio, Move to Orchestrate, or Rebuild in Extend](https://kiweely.com/guides/ai-triage-studio-orchestrate-or-extend-evidence)
-   [Reading Integration Launch Attachments, Calling SOAP Integrations API, and Uploading ZIPs to Workday Drive in O4I](https://kiweely.com/guides/workday-orchestrate-read-integration-attachment-retrieval-service)
-   [Generating UUIDs with random.randomUUID() and Fixing stringAtJsonPath().toNumber() in Orchestrate](https://kiweely.com/guides/workday-orchestrate-randomuuid-stringatjsonpath-tonumber)
-   [Why Send Workday RaaS Request fails with ‘Key not found’ (HTTP 202) or times out at 5 minutes](https://kiweely.com/guides/workday-orchestrate-raas-key-not-found-202-5-minute-timeout)
-   [Fixing ‘not a simple type launch parameter (Text, Number, Boolean, Date)’ on blank O4I launch parameters](https://kiweely.com/guides/workday-orchestrate-null-launch-parameter-not-simple-type)
-   [Storing and Migrating External Client CredStore OAuth Credentials and Masked Integration Attributes in Workday Orchestrate](https://kiweely.com/guides/workday-orchestrate-migrate-external-client-credstore-secrets)
-   [JSONPath Logical Filter Expressions and Wildcard XPaths in Workday Orchestrate](https://kiweely.com/guides/workday-orchestrate-jsonpath-logical-filters-xpath-wildcards)

### From the blog on Orchestrate

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

-   [Kiweely Roots vs Workday EIB, Studio, and Orchestrate](https://kiweely.com/blog/kiweely-roots-vs-workday-eib-studio-orchestrate)
-   [Orchestrate, an iPaaS, or Kiweely Roots](https://kiweely.com/blog/orchestrate-ipaas-or-kiweely-roots)
-   [Codex for Orchestration JSON: Catching the 25-Second Sync Trap Before Deploy](https://kiweely.com/blog/codex-orchestration-json-25-second-sync-trap)

## 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.
