Skip to main content
Documentation
Documentation
Administrator Guide
Last Updated: 2026-04-03
Reference: Integrations and Web Service Limits

Reference: Integrations and Web Service Limits

This topic summarizes Workday's Service Limits for Integrations and Web Services and provides best practice recommendations.
When you reach or exceed any integration or web service request limits set forth below, Workday may, in its sole discretion, (a) throttle your use of the integration or web service; or, (b) suspend your access to the integration or web service until usage is brought within the limit. In the event Workday makes available products or services which allow you to purchase additional capacity for a particular integration or web service, you can elect to purchase those products or services subject to any applicable terms and conditions.
Category
Limits/Boundaries
Adobe Sign Integration API Requests
API transactions for Adobe Sign vary by type of subscription. Learn more about Adobe Acrobat Sign transaction limits.
API Requests
API requests throttled under high load:
  • Workday Web Services (WWS) SOAP API.
  • Workday Reports-as-a-Service (RaaS) API.
  • Workday REST API.
Workday rejects API requests when other requests overload tenant resources and returns an HTTP response code of:
  • 429 Too Many Requests: For REST and RaaS APIs.
  • 500 Internal Service Error: For SOAP and RaaS APIs. The 500 error code can sometimes be caused by too many requests. In this case, retry additional requests after a brief pause.
If you encounter the response code, we recommend that you implement:
  • An exponential back-off retry mechanism for the process that generates the API requests.
  • Caching.
For Paged API requests, avoid setting a strict HTTP timeout for page 1 requests to ensure that Workday has enough time to build a cache for subsequent calls. Page 1 requests often take longer to process, as Workday gathers all results for them and stores them in a cache. The limits for persisting the caches are:
  • 2 hours between paged requests
  • 30 minutes after you request the last page
For gateway request size limits, see the Workday Web Service Requests row in this table.
For Workday APIs that upload data, if a request upload stalls for too long, Workday may terminate the connection as a protective measure. The request upload idle timeout applies to a single request, and includes idle times between consecutive chunks of data.
API Extract Requests
API extract interfaces for Workday Reports-as-a-Service (RaaS).
Customers can perform these maximum extract request volumes in total across all API extract interfaces:
Customer Size
Maximum Requests per 24-hour Period
Maximum Requests in a single 60-minute Period
Less than 3,500 workers (ME)
75,000
15,000
Less than 10,000 workers (LE)
100,000
30,000
Less than 100,000 workers (LE)
250,000
75,000
More than 100,000 workers
350,000
100,000
Connectors and EIBs: Processing Limits
Processing limits for Workday integrations vary by type of integration (long-running or standard).
  • Long-running integration: all EIBs and any integrations listed in Connectors with Extended Processing Limits. The processing limit for long running integrations is 30 hours.
  • Standard integration: any integration that isn't long-running. The processing limit for standard integrations is 4 hours (2 hours for IMPL tenants).
For an EIB, Workday applies limits for each individual step. Example: On an outbound EIB:
  • On the delivery step, Workday applies the 30-hour limit.
  • On the data source step, Workday applies a 6-hour HTTP processing request limit for Workday Web Services and Reports-as-a-Service (RaaS).
Connectors and EIBs: Number of Concurrent Integrations
  • Long-running integrations: up to 5 concurrent integrations if resources are available at that time.
  • Standard integrations: up to 25% of available processing capacity. Available processing capacity is capacity that is currently not in use.
Long-running integrations are all EIBs and any integrations listed in Connectors with Extended Processing Limits.
To avoid queuing during busy peak hours, Workday strongly recommends that you select a random 5 min integration start time (Example: 9:10, 9:15, 9:25) instead of selecting the top of the hour.
Connectors: Runtime (including Document Transformation)
  • Total for all files generated during the integration run: 3 GB (compressed).
  • Any single file generated during the integration run: 1 GB (compressed).
  • Memory used during processing: 27 GB.
  • Processing time: Up to 4 hours. Workday allows some connectors to run for up to 30 hours. Any pause in processing doesn't count toward the limit.
  • Document transformations can consume several times the amount of memory that the source data requires.
DocuSign Integration API Requests
  • Hourly API call limits: 3000 by default.
  • Burst API call limits: 500 calls per 30 seconds.
These numbers are currently accurate. For more information, refer to DocuSign API Rate Call Limits or contact DocuSign directly.
EIBs: Dynamic File Names
Filenames can only be between 1-255 characters long and can’t be more than 1 line.
EIBs: Inbound Document Retention
Sixty (60) days for these troubleshooting files:
  • ErrorsAndWarningsSpreadsheet.xml
  • FailureReport.html
  • OriginalDataWithErrors.xml
Workday has no retention policy for XSLT or XML spreadsheet attachments. They remain attached to their integration events indefinitely.
EIBs: Inbound File Size
  • EIB spreadsheets using SFTP, FTPS, REST, Amazon Simple Storage Service: 1 GB for XML and 300MB for XLSX.
  • Files uploaded from a browser: 30 MB.
EIBs: Outbound Document Retention
Document Retention Policy (in Days): 180 days.
EIBs: Runtime
Processing time for:
  • Outbound EIBs retrieving custom report or web service data: 30 hours. Any pause in processing doesn't count toward the 30-hour limit.
  • Inbound EIBs loading Workday Web Service or Custom Object data: 5 hours.
  • Inbound EIBs creating the Failure Report, Errors & Warnings spreadsheet, and Add Errors to Attachment spreadsheet: 2 hours.
EIBs: Runtime on EIBs with Custom XSLT Transformations
Data transformation: 27 GB.
EIBs with custom XSLT transformations can consume several times the amount of memory that the source data requires.
Recommendations:
  • Run the EIB with different filters. Use either custom report filters by maintaining launch parameters for the web service data source.
  • Review your custom XSLT for possible processing inefficiencies.
  • Convert your EIB to a Workday Studio integration.
EIBs: Spreadsheet with Data Size
  • Data size: 300 MB.
  • Generation time: 2 hours.
Workday splits output across multiple spreadsheets when:
  • You generate a spreadsheet with data.
  • The web service operation generates between 20 MB and 300MB of data.
Workday recommends that you filter your data by selecting
Edit Template with Data Options
 in the
Data
 tab of the template model.
Email Notification File Size
20 MB.
Integrations: Allow-lists for External Endpoint IP Addresses
Workday doesn't support allow lists for vendor IP addresses for integrations.
Integrations: AS2 Outbound File Size
Sending files from Workday to an external endpoint using EIB or the Delivery Service: 200 MB.
Integrations: Data Sources
  • All Integration Events: 50,000 instances.
  • All Integration Events in Date Range: 50,000 instances.
  • Get all Integration Messages: 50,000 instances.
  • Integration Message in Date Range with Query: 10,000 instances.
Workday applies these limits after the data source filters the data, but before standard or custom report filters. To optimize data extraction, Workday recommends using data sources with date ranges when applicable.
Integrations: Integration System User Account Time Zone Limits
Integration System User (ISUs) accounts always retrieve data based on the Pacific time zone.
Integrations: Scheduled Integration Launch and Completion
Varies depending on the resources required and integration work. Workday recommends that you:
  • Don't implement an integration or external application that relies on another integration running or completing at a specific time. Instead, include the 2 integrations as steps in a business process so that the second integration launches only after the first integration completes successfully.
  • Contact Workday Support only if an integration consistently takes an abnormally long time to complete.
Integration Event Maximum Processing Time
7 days.
Exception: ADP Payroll CSV integrations.
Integrations: HTTP Request Processing Time
6 hours, including Workday Web Services and Reports-as-a-Service (RaaS).
These integrations make HTTP requests:
  • EIBs.
  • Studio integrations.
  • Cloud Connect integrations.
Integrations: S/FTP/S Request Time
6 hours for these requests:
  • FTP
  • SFTP
  • FTPS
Integrations: Document Delivery Service and Retrieval Service
  • 5000 integration documents per integration run.
  • Total of all files generated during the integration run: 3 GB (compressed).
  • Single file generated during the integration run: 1 GB (compressed).
Message Queue Size
  • 10 message queues per tenant.
  • 64,000 messages per queue.
  • Message size: 1 GB (compressed).
  • All messages expire after 7 days.
Studio Integrations: Consolidated Report and Log File Retention and Size
  • File retention: 60 days.
  • Size: 50 million characters (approximately 48 MB).
Studio Integrations: Disc Size
13 GB per integration event.
Studio Integrations: Put Integration Message Sub-Assembly
500 times in an integration event. This limit doesn't include:
  • Messages with attachments and targets.
  • Messages that change the integration event status.
Studio Integrations: Runtime
  • Total of all files generated during the integration run: 3 GB (compressed).
  • Single file generated during the integration run: 1 GB (compressed).
  • Memory used during processing: 12 GB. Integrations can use several times the amount of memory that the output files require.
  • Time limitation: 2 hours.
Studio Integrations: File-Backed Managed Data (FBMD) Limit
The maximum document size that a Studio integration can handle: 16 GB.
Workday Reports-as-a-Service (RaaS)
Advanced custom report enabled for web services and exposed for integrations: 2 GB.
Workday Web Service Requests
  • Incoming Import web service requests: 2 GB.
  • All other incoming web service requests: 500 MB.
  • Web service responses for outbound operations: 2 GB.
Workday doesn't log GET requests or unsuccessful requests. You can specify external integration HTTP headers with your requests to enable tracking in server logs.
Workday Web Services: Attachments
For SOAP and REST:
  • Maximum Attachment Size: 30MB
  • Maximum Image Size: 30MB
Workday Web Services: Currency
Decimal (total_digits, fraction_digits).
  • Example:
    decimal (18, 6)
     implies that the given SOAP API has a limit of a maximum of 18 digits with 6 of them being decimal digits.
  • It's a dynamic value specified in the
    Workday Web Services (WWS) Directory
     on Community under the
    Type/Value
    column.
Workday Web Services: Date
Workday uses
YYYY-MM-DD
 format for date fields. When you add a time zone value to this date field, Workday removes it before persisting the field.
Workday Web Services: Date and Time
Workday uses
YYYY-MM-DDThh: mm:ss.fffZ
 for zero offset from UTC.
  • Fff represents a fractional second. T indicates a time. Z indicates a zero offset.
  • Example: 2022-08-26T13:05:46.493Z
  • Send the requests in ISO 8601 format.
  • Specify any time zone offset from Coordinated Universal Time (UTC).
  • Provide both minutes and seconds in the time component of a datetime in a request. Seconds can have an optional fraction.
  • Workday returns Datetimes in ISO 8601 format. Times are in Pacific Time, either as UTC-07:00 or UTC-08:00. These options vary according to which web service API version that you use.
Workday Web Services: HTTP Header Size and SOAP Message Size
HTTP Header size of all web service requests: 16 kilobytes (KB).
Workday Web Services: Integer
Decimal (total_digits, fraction_digits)>0
  • Example:
    decimal (4, 0)>0
     implies that the given SOAP API has a limit of 4 digits, no fractions, and no negative numbers.
    decimal (2, 1)
     implies that the given SOAP API has a limit of 2 digits, 1 fraction, and negative numbers.
  • It's a dynamic value specified in the
    Workday Web Services (WWS) Directory
     on Community under the
    Type/Value
    column.
  • Workday uses integer attributes only for custom integer fields used in custom objects.
Workday Web Services: Response Size Limit
Maximum number of instances in a web service response: 1 million.
You can reduce the number of instances returned by using request criteria, response filters, or date ranges.
Workday doesn't log web service responses. You can specify external integration HTTP headers with your requests to enable tracking in server logs.
Workday Web Services: Rich Text String Size Limit
Maximum number of characters: 1,048,576 or 1MB.