---
title: "Workday API Attachment Limits, File Types & Virus Rules"
description: "Workday REST and SOAP attachment upload limits (30 MB files, 10 MB images), blocked extensions, virus scanning gaps on web services, and document security."
url: https://kiweely.com/guides/workday-attachment-upload-virus-scan-size-mime-rules-api
---

# Workday API Attachment Rules: File Size Limits, Allowed MIME Types, and Doctor’s Note Uploads

Workday caps API and UI file attachments at 30 MB (10 MB for tenant images), blocks executable extensions such as exe, bat, js, and vbs in Edit Tenant Setup - System, skips automatic virus scanning on web service uploads, and secures medical notes via Document Category Security Segments.

-   **Checked** against Workday on November 15
-   Applies to **Workday Attachments & APIs**
-   6 min read
-   Published November 15
-   By Kiweely

Workday enforces a fixed **30 MB (`30,720 KB`) maximum file size** on transactional attachments (`10,240 KB` for standard tenant images), permanently blocks 16 executable and script extensions (`exe`, `bat`, `js`, `vbs`, `lnk`, and related types) alongside any tenant-specific allowlist configured in **Edit Tenant Setup - System**, and **does not run Workday’s built-in virus scanner on files uploaded via REST or SOAP web services**. Any external form, mobile app, or chat workflow that uploads expense receipts or medical leave certificates into Workday must therefore run malware scanning and MIME/size checks *before* forwarding the file, and bind sensitive attachments to segmented Document Categories so front-line supervisors cannot open clinical records.

Uploading files into Workday fails silently or leaks sensitive documents when developers treat an attachment endpoint like a generic S3 bucket. Below are the exact payload contracts, tenant setup gates, virus-scanning rules, and security domains governing attachments across Leave of Absence, Expense, and Worker Documents.

## Workday Attachment Limits, File Types, and Scanning Rules at a Glance

Check these tenant-wide boundaries before writing upload code or sizing reverse-proxy body limits:

| Boundary | Workday Rule / Limit | Controlling Task or Documentation |
| --- | --- | --- |
|  **Max Attachment Size** |  **30 MB (`30,720 KB`)** per file across UI, REST, and SOAP (non-configurable) |  **Edit Tenant Setup - System** (*Maximum Attachment Size (KB)*) |
|  **Max Image Size** |  **10 MB (`10,240 KB`)** in tenant setup (`30 MB` max on WWS image operations) |  **Edit Tenant Setup - System** (*Maximum Image Size (KB)*) |
|  **Total Tenant Document Storage** |  **10 TiB (`10,240 GB`)** across resumes, receipts, worker docs, and reports |  **Platform Consumption Console** (*Consumption Usage* tab) |
|  **Permanently Blocked Extensions** | `bas`, `bat`, `com`, `exe`, `js`, `lnk`, `ocx`, `reg`, `sct`, `sys`, `vb`, `vbe`, `vbs`, `wsc`, `wsf`, `wsh` |  **Edit Tenant Setup - System** (*File Type Setup Instructions*) |
|  **Tenant Allowlist Mode** |  *Allow All File Types* (default) vs. *Allow ONLY Specific File Types* (e.g., `pdf`, `jpg`, `png`, `docx`) |  **Edit Tenant Setup - System** (*File Type Setup Instructions*) |
|  **Password-Protected / Corrupted PDFs** | Rejected when rendering/printing Business Forms; avoid encrypted PDFs | Document & Printing Limits |
|  **Built-In Virus Scanning** | Scans UI uploads (`Add Worker Document`, `Create Expense Report`, career sites); **skips web services & integrations** | Workday Virus Scanning Limitations |
|  **SOAP `File_Name` & `Content_Type` Length** | `File_Name` max **255 chars** (single line); `Content_Type` max **80 chars** | `Business_Process_Attachment_DataType` XSD |

## Two REST Multipart Patterns vs. SOAP Base64 Attachments

Workday exposes three distinct wire formats depending on whether you attach a file to an existing REST resource, create a new REST object with inline attachments, or submit a Business Process via SOAP.

### Pattern 1: REST Sub-Resource Upload (`attachmentContent` on Existing Objects)

Services such as Expense (`POST /expense/v1/{tenant}/entries/{ID}/attachments`), Procurement (`POST /procurement/v3/{tenant}/requisitions/{ID}/attachments`), Accounts Payable (`POST /supplierInvoiceRequests/{ID}/attachments`), and Recruiting (`POST /prospects/{ID}/resumeAttachments`) accept `multipart/form-data` with a single form field named `attachmentContent`:

Works

```
POST /api/expense/v1/tenant_dpt1/entries/4d718d459cce01000c6fb285efa20000/attachments HTTP/1.1
Host: wd5-services1.workday.com
Authorization: Bearer <employee_oauth_access_grant>
Content-Type: multipart/form-data; boundary=----WorkdayUploadBoundary

------WorkdayUploadBoundary
Content-Disposition: form-data; name="attachmentContent"; filename="parking-receipt-nov14.pdf"
Content-Type: application/pdf

<raw_pdf_bytes>
------WorkdayUploadBoundary--
```

Workday responds with the created attachment WID, resolved MIME `contentType` descriptor (for example, `application/pdf`), byte `fileLength`, and `fileName`.

### Pattern 2: REST Composite Create (`jsonData` + `cid:` File Parts)

When creating a parent object and its attachments in one atomic call—such as `POST /request/v1/{tenant}/requests` or `POST /staffing/v6/{tenant}/workers/{ID}/checkInTopics`—send `multipart/form-data` combining a `jsonData` part and one or more binary file parts referenced via Content-ID (`cid:file1`, `cid:file2`):

Works

```
POST /api/request/v1/tenant_dpt1/requests HTTP/1.1
Host: wd5-services1.workday.com
Authorization: Bearer <employee_oauth_access_grant>
Content-Type: multipart/form-data; boundary=----WorkdayCompositeBoundary

------WorkdayCompositeBoundary
Content-Disposition: form-data; name="file1"; filename="medical-clearance.pdf"
Content-Type: application/pdf

<raw_pdf_bytes>
------WorkdayCompositeBoundary
Content-Disposition: form-data; name="jsonData"
Content-Type: application/json

{
  "description": "Ergonomic accommodation request",
  "requestType": { "id": "8aae3f174909012f50f2ff5e505f5a09" },
  "questionnaireResponses": {
    "questionnaireAnswers": [
      {
        "questionItem": { "id": "8aae3f174909011301757039505f4d09" },
        "questionnaireAttachments": [
          { "file": "cid:file1" }
        ]
      }
    ]
  }
}
------WorkdayCompositeBoundary--
```

### Pattern 3: SOAP Business Process Attachments (`Request_Leave_of_Absence` & `Maintain_Worker_Documents`)

For Business Processes whose initiation payload lives in Workday SOAP Web Services—such as attaching a physician’s certification to `Request_Leave_of_Absence` in `Absence_Management` (`v45.1`) or uploading a standalone worker file via `Put_Worker_Document` in `Human_Resources`—embed Base64-encoded bytes inside `Business_Process_Attachment_Data` (or `Worker_Document_Data`):

Works

```
<wd:Business_Process_Parameters>
  <wd:Auto_Complete>false</wd:Auto_Complete>
  <wd:Run_Now>true</wd:Run_Now>
  <wd:Business_Process_Attachment_Data>
    <wd:File_Name>physician-certification-2026-11.pdf</wd:File_Name>
    <wd:Event_Attachment_Description>FMLA medical certification</wd:Event_Attachment_Description>
    <wd:Event_Attachment_Category_Reference>
      <wd:ID wd:type="Document_Category_ID">LEAVE_MEDICAL_DOC</wd:ID>
    </wd:Event_Attachment_Category_Reference>
    <wd:File>JVBERi0xLjUKJeLjz9MK...</wd:File>
    <wd:Content_Type>application/pdf</wd:Content_Type>
  </wd:Business_Process_Attachment_Data>
</wd:Business_Process_Parameters>
```

Watch Base64 Overhead and Category Validation

Base64 encoding inflates payload size by roughly 33%, though Workday measures the 30 MB attachment cap against the decoded file (`500 MB` incoming gateway limit applies to the overall non-Import SOAP envelope). Only include `<wd:Event_Attachment_Category_Reference>` if the Business Process type supports attachment categories—otherwise Workday returns a `Validation_Fault` (*“This Business Process Type has been configured to not accept Attachment Categories”*).

## Critical Security Gap: Web Service Uploads Bypass Workday Virus Scanning

Workday’s **Concept: Virus Scanning** documentation states a crucial operational boundary that catches many InfoSec teams off guard: Workday automatically scans browser uploads on tasks like **Add Worker Document**, **Create Expense Report**, **Create Supplier Invoice**, and external career sites, **but Workday’s virus scanning service does NOT scan files imported using web services and integrations** (nor files larger than 30 MB or certain media streams).

Whenever an external portal, mobile app, or chat integration accepts a PDF or photo from an employee’s phone and forwards it over Workday REST or SOAP:

1.  **Scan in memory before calling Workday:** Stream the uploaded file through an antivirus engine (such as ClamAV or cloud malware inspection) in RAM before opening the outbound request to Workday, and drop infected payloads immediately without writing them to disk.
2.  **Verify magic bytes, not just file extensions:** Confirm that a file named `doctor-note.pdf` actually begins with `%PDF-` (`25 50 44 46 2D`) or valid JPEG/PNG/HEIC headers, and convert mobile `HEIC` camera photos to `JPG` or `PDF` if **Edit Tenant Setup - System** uses *Allow ONLY Specific File Types* without `heic` enabled (and if downstream Expense Business Form PDF printing requires `JPG`, `PNG`, `GIF`, `TIFF`, `BMP`, or `PDF`).
3.  **Avoid stalled chunked uploads:** Workday enforces a request upload idle timeout across consecutive data chunks and terminates stalled upload connections to protect gateway resources. Validate and buffer/stream cleanly over fast TLS connections.

## Securing Doctor’s Notes and Medical Attachments on Leave Events

When a worker attaches a doctor’s note to **Request Leave of Absence** (a worker-related business process, which also adds the attachment to the worker’s document file), **default inheritance can expose that note to the worker’s direct manager** if attachment security is left unconfigured!

By default, if you leave **Attachment Settings in BP Toolbar** blank on a Business Process Security Policy, Workday automatically inherits attachment view/edit permissions from the security groups assigned to each Business Process step—meaning a `Manager` assigned an *Approval* step on `Request Leave of Absence` could view the attached medical note unless segmented.

Lock down clinical and accommodation attachments with four tenant steps:

1.  **Check the “Most Recent Change Wins” Tenant Trap:** Attachments can be toggled globally on **Edit Tenant Setup - Business Processes** (*Enable Attachments*) or per workflow on the **Business Process Security Policy**. When the two conflict, **Workday honors whichever task was saved most recently**—even if someone edited an unrelated field on **Edit Tenant Setup - Business Processes**! Always check both audit trails if an upload suddenly fails.
2.  **Create a Dedicated Medical Document Category:** Run **Maintain Document Categories** (secured by *Set Up: Tenant Setup - Document Categories*) and create `Leave / Medical Documentation` (`LEAVE_MEDICAL_DOC`).
3.  **Segment Access Away from Line Managers:** Run **Create Document Category Security Segment** to isolate `LEAVE_MEDICAL_DOC`, bind it to a **Segment-Based Security Group** containing only `Absence Partner` / `HR Administrator` roles (plus `Employee As Self` if workers should upload/view their own), and exclude supervisory `Manager` groups.
4.  **Configure the Business Process Policy & Activate:** Open the **Request Leave of Absence** Business Process Security Policy → **Edit** → **Attachment Settings in BP Toolbar**, assign your segmented security groups to **View Permissions**, **Edit Permissions**, and **Manage Attachment Permissions**, verify self-service worker document domains (*Self-Service: Add Worker Documents* in the *Personal Data* functional area where applicable), and run **Activate Pending Security Policy Changes**.

When employees upload a receipt or leave document through a custom screen built with [Kiweely Leaf](https://kiweely.com/leaf) (coming next), Leaf streams the file statelessly without storing HR documents at rest on Kiweely servers and executes the Workday upload under that signed-in employee’s own OAuth permissions—honoring every Document Category Security Segment and Business Process policy in your tenant.

## Frequently asked questions

### Does Workday automatically scan files uploaded via REST or SOAP APIs for viruses?

No. While Workday runs automatic virus scanning on browser uploads in tasks such as Add Worker Document, Create Expense Report, and Apply to Job, Workday's virus scanning service explicitly does not scan files imported through web services and integrations or files over 30 MB.

### What is the maximum file size for a Workday attachment uploaded via REST or SOAP?

The hard tenant ceiling is 30 MB (30,720 KB) per attachment across both the Workday UI and SOAP/REST web services, and 10 MB (10,240 KB) for tenant image uploads (up to 30 MB on specific web service image endpoints). Administrators cannot raise these limits in Edit Tenant Setup - System.

### Where do Workday administrators restrict allowed file extensions for uploads?

In Edit Tenant Setup - System under System Setup (File Type Setup Instructions), administrators choose between Allow All File Types (minus Workday's permanently blocked executable extensions like exe, bat, js, lnk, and vbs) or Allow ONLY Specific File Types.

### How do I keep managers from viewing sensitive medical or doctor's note attachments on a Leave of Absence event?

Create a dedicated Document Category (via Maintain Document Categories), restrict it with Create Document Category Security Segment to a segment-based security group (such as Leave Partners), and configure Attachment Settings in BP Toolbar on the Request Leave of Absence Business Process Security Policy.

## Sources checked

-   [Concept: Workday REST API File Attachments](https://developer.workday.com/documentation/dht1640644225980)
-   [Reference: Document, File Size, and Printing Limits](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/it-administrator-resources/limitations-and-availability/dan1370796659943.html)
-   [Reference: Edit Tenant Setup - System](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/tenant-setup/dan1370797880489.html)
-   [Concept: Virus Scanning](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/it-administrator-resources/cfj1595636131851.html)
-   [Steps: Enable Attachments on an Individual Business Process](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/manage-business-processes/ala1404761315058.html)
-   [Maintain Worker Documents](https://doc.workday.com/admin-guide/en-us/human-capital-management/worker-information/worker-documents/dan1370796407197.html)

## Related guides

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

-   [### Authenticating Workday SOAP Web Services with a User-Delegated OAuth Bearer Token Send Workday SOAP requests with an HTTP Authorization Bearer header issued from a user-delegated OAuth 2.0 Authorization Code grant and leave the SOAP XML Header element empty. Workday evaluates both the API Client Functional Area scope and the signed-in worker’s Integration Permissions.](https://kiweely.com/guides/workday-soap-api-bearer-token-user-delegated-oauth)
-   [### Diagnosing Workday REST API 403 Forbidden: Missing Client Scope vs. Worker Domain Security A Workday REST API 403 Forbidden means OAuth authentication succeeded, but authorization failed at one of five checkpoints: API Client Functional Area scope, stale pre-edit access grant, Report/Task Domain Security Policy, Business Process Security Policy, or unactivated pending policy changes.](https://kiweely.com/guides/workday-rest-api-403-forbidden-user-security-vs-client-scope)
-   [### Parsing Workday Business Process Custom Validation Errors Returned by REST and SOAP APIs Workday REST APIs return HTTP 400 JSON payloads containing an errors array with code, field, path, and severity (Critical or Warning), whereas Workday SOAP Web Services return HTTP 500 envelopes containing Validation\_Fault (with Xpath) or Processing\_Fault elements.](https://kiweely.com/guides/workday-business-process-validation-errors-rest-soap-responses)
-   [### How Workday Audits Business Processes Initiated via REST or SOAP Web Services Workday records every web-service-initiated business process in the Full Process Record and View Audit Trail under the authenticated Workday account. Whether that audit trail shows a real employee or a shared system bot depends on whether the caller used user-delegated OAuth or an ISU.](https://kiweely.com/guides/workday-business-process-audit-trail-initiated-via-web-service)

### More guides on Integrations and APIs

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

-   [Scoping Workday API Client Functional Areas for Least-Privilege Access](https://kiweely.com/guides/workday-api-client-functional-areas-least-privilege-scoping)
-   [Submitting and Validating Time-Off Requests with the Workday Absence REST API](https://kiweely.com/guides/workday-absence-management-rest-api-request-time-off)
-   [Reading Current Benefits Elections and Dependents Through Workday Self-Service APIs](https://kiweely.com/guides/workday-view-benefits-elections-dependents-beneficiaries-api)
-   [Auditing External API Calls in Workday Sign-On History and Activity Logs](https://kiweely.com/guides/workday-view-api-client-audit-logs-sign-on-history)
-   [Entering Time Blocks and Check-In/Check-Out Events via Workday Time Tracking APIs](https://kiweely.com/guides/workday-time-tracking-api-clock-in-out-enter-time)
-   [Workday Expenses REST API: create a Quick Expense, upload a receipt and submit an Expense Report](https://kiweely.com/guides/workday-expenses-rest-api-receipt-attachments-expense-lines)
-   [Designing for Workday Tenant API Concurrency and Rate Limits During Peak Employee Traffic](https://kiweely.com/guides/workday-api-rate-limits-concurrency-workforce-self-service)
-   [Calling Workday RaaS Reports with User-Delegated OAuth Instead of an ISU](https://kiweely.com/guides/workday-raas-user-delegated-oauth-vs-isu-basic-auth)

### From the blog on Integrations and APIs

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

-   [The Slow Change Cycle in Workday Studio (and How to Break It)](https://kiweely.com/blog/workday-studio-slow-change-cycle)
-   [Kiweely builds, deploys and runs a Workday Studio integration from one request](https://kiweely.com/blog/workday-studio-integration-built-deployed-and-run)
-   [Why does a Workday EIB load fail, and how do you get a clean load the first time?](https://kiweely.com/blog/why-workday-eib-load-fails)

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