---
title: "Approve, Deny & Send Back Workday BP Steps via REST & SOAP"
description: "How to approve, deny, send back, reassign, and complete To Do steps on awaiting Workday business processes via businessProcess v1 REST and Integrations SOAP."
url: https://kiweely.com/guides/workday-business-process-approve-deny-rest-soap-api
---

# Approving, Denying, and Sending Back Workday Business Process Steps via REST and SOAP APIs

Advance pending Workday workflow steps via businessProcess v1 REST endpoints (/eventSteps/{ID}/approve, /deny, /sendBack, /toDo, /reassign) using the Event Record WID, or via Integrations SOAP operations (Approve\_Business\_Process, Deny\_Business\_Process, Send\_Back\_Business\_Process).

-   **Checked** against Workday on November 15
-   Applies to **Workday Business Processes & APIs**
-   7 min read
-   Published November 15
-   By Kiweely

To advance an awaiting-action workflow step in Workday, call the **`businessProcess/v1`** REST resource on the specific **`Event Record`** Workday ID (`POST /eventSteps/{ID}/approve`, `/deny`, `/sendBack`, `/toDo`, or `/reassign`), or invoke the **`Integrations`** SOAP web service (`Approve_Business_Process`, `Deny_Business_Process`, `Send_Back_Business_Process`, `Reassign_Business_Process_Step`). Use the REST `eventSteps` endpoints whenever a user-delegated OAuth client acts on a specific **My Tasks** item, especially on business processes with parallel approval branches.

Most `400 Bad Request` and SOAP `Validation_Fault` failures when advancing workflows come from three mismatches: passing the parent **`Event`** WID where Workday expects the step’s **`Event Record`** WID, calling `/approve` on a **`To Do`** or **`Action`** step type, or violating tenant comment rules (`Disable Comments` vs. required `comment` / `reason` fields).

## REST `businessProcess/v1` vs. SOAP `Integrations` Step Operations

Before writing client code, verify which ID type, security domain, and payload contract each operation expects:

| Workflow Action | REST `businessProcess/v1` Endpoint | Target Path ID | SOAP `Integrations` Operation | SOAP Target Element | Required Body Fields (REST) |
| --- | --- | --- | --- | --- | --- |
|  **Approve Step** | `POST /eventSteps/{ID}/approve` | `Event Record` WID | `Approve_Business_Process` | `Event_Reference` (WID or Ref ID) | `comment` (unless comments disabled) |
|  **Deny Step** | `POST /eventSteps/{ID}/deny` | `Event Record` WID | `Deny_Business_Process` | `Event_Reference` (WID or Ref ID) | `id`, `comment`, and `stepAction.id` (when multiple actions exist) |
|  **Send Back Step** | `POST /eventSteps/{ID}/sendBack` | `Event Record` WID | `Send_Back_Business_Process` | `Event_Reference` (`Action_Event` WID) | `id`, `to.id` (target prior step), `reason` |
|  **Complete To Do** | `POST /eventSteps/{ID}/toDo` | `Event Record` WID |  *(Event-specific / service step)* | — | `stepAction.id` (`Submit` or `Save for Later`); optional `comment` |
|  **Reassign Step** | `POST /eventSteps/{ID}/reassign` | `Event Record` WID | `Reassign_Business_Process_Step` | `Event_Record_Reference` (WID) | `addAssignees` and/or `removeAssignees`; optional `comment` |
|  **Cancel / Rescind Event** | `POST /events/{ID}/cancel` or `/rescind` | Parent `Event` WID | `Cancel_Business_Process` / `Rescind_Business_Process` | `Event_Reference` (`Action_Event` WID) | `comment` |

All `businessProcess/v1` step-action endpoints are secured by the **Core Navigation** and **Public Business Processes** domains (available under Functional Areas including *Tenant Non-Configurable*, *Benefits*, and *Adaptive Planning*), **intersected** with the authenticated caller’s view and action permissions on the underlying business process security policy.

## Step 1: Confirm `Event Record` WID and `stepType` Before Acting

Never hardcode `/approve` for every item in a worker’s queue. First, inspect the pending step via [Workday’s `inboxTasks` or `eventSteps` read endpoints](https://kiweely.com/guides/workday-inbox-my-tasks-awaiting-action-rest-wql):

http

```
GET /ccx/api/businessProcess/v1/{tenant}/eventSteps/7ad3143787b64ee8937b33fbc1198356 HTTP/1.1
Accept: application/json
```

Check three properties in the response before choosing an action endpoint:

1.  **`status.descriptor`:** Confirm it equals `"Awaiting Action"`.
2.  **`stepType.descriptor`:**
    -   `"Approval"` or `"Approval Chain"` or `"Consolidated Approval"` -> eligible for `/approve`, `/deny` (if allowed by policy), or `/sendBack`.
    -   `"To Do"` -> must use `/toDo` (calling `/approve` fails with `A190`).
    -   `"Complete Questionnaire"` -> must use `POST /eventSteps/{ID}/questionnaire` with `stepAction` and `questionnaireResponse`.
    -   Domain-specific `"Action"` steps (for example, *Enter PayGroup* during *Hire* or *Accept Shift Swap*) require completing the functional domain payload rather than a bare `/approve` call.
3.  **`event.id`:** Save the parent `Event` WID if you also need to read `GET /events/{ID}/attachments`, `/comments`, or `/completedSteps`.

## Step 2: Executing REST `approve`, `deny`, `sendBack`, and `toDo` Calls

Every successful `POST` to a `businessProcess/v1` step action returns **`HTTP 201 Created`** with the updated step payload and resulting `eventStatus`.

### Approving an Approval Step (`/approve`)

http

```
POST /ccx/api/businessProcess/v1/{tenant}/eventSteps/7ad3143787b64ee8937b33fbc1198356/approve HTTP/1.1
Content-Type: application/json
Accept: application/json

{
  "comment": "Reviewed coverage and approved."
}
```

### Denying an Approval Step (`/deny`)

`POST /eventSteps/{ID}/deny` requires the step’s `id` in the JSON body alongside `comment` (and `stepAction` with `{ "id": "..." }` when multiple step actions are available on that step):

http

```
POST /ccx/api/businessProcess/v1/{tenant}/eventSteps/7ad3143787b64ee8937b33fbc1198356/deny HTTP/1.1
Content-Type: application/json
Accept: application/json

{
  "id": "7ad3143787b64ee8937b33fbc1198356",
  "comment": "Duplicate submission for the same dates; Nov 24-25 request is already approved."
}
```

### Sending Back a Step to a Prior Actor (`/sendBack`)

Before calling `/sendBack`, discover which prior steps the workflow allows sending back to via `GET /ccx/api/businessProcess/v1/{tenant}/values/sendBack/to/` (passing the step context). Then submit `id`, `to` (the target step WID), and `reason`:

http

```
POST /ccx/api/businessProcess/v1/{tenant}/eventSteps/7ad3143787b64ee8937b33fbc1198356/sendBack HTTP/1.1
Content-Type: application/json
Accept: application/json

{
  "id": "7ad3143787b64ee8937b33fbc1198356",
  "to": {
    "id": "d9e4108c446c11de98360015c5e6daf6"
  },
  "reason": "Please attach itemized hotel folio showing daily room rate and tax breakdown."
}
```

### Completing a `To Do` Step (`/toDo`)

Workday defines fixed WIDs for `stepAction` on `POST /eventSteps/{ID}/toDo`:

-   **Submit:** `"133d5c88baa64136aab041c1d2e9ed53"`
-   **Save for Later:** `"d9e41d34446c11de98360015c5e6daf6"`

json

```
{
  "stepAction": {
    "id": "133d5c88baa64136aab041c1d2e9ed53"
  },
  "comment": "Badge and safety orientation checklist completed."
}
```

## Step 3: Advancing Steps via SOAP (`Integrations` Service)

When working with legacy integrations or workflows where only the parent `Event` WID or Reference ID is on hand, Workday’s **`Integrations`** WSDL (`https://{hostname}/ccx/service/{tenant}/Integrations/v43.0`) provides `Approve_Business_Process`, `Deny_Business_Process`, and `Send_Back_Business_Process`. These SOAP operations accept an OAuth 2.0 Bearer access token header in place of WS-Security username headers when called on behalf of a signed-in worker.

### SOAP `Approve_Business_Process` Example

xml

```
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
                  xmlns:bsvc="urn:com.workday/bsvc">
  <soapenv:Header/>
  <soapenv:Body>
    <bsvc:Approve_Business_Process_Request bsvc:version="v43.0">
      <bsvc:Event_Reference>
        <bsvc:ID bsvc:type="WID">f1208b90446c11de98360015c5e6daf6</bsvc:ID>
      </bsvc:Event_Reference>
      <bsvc:Approve_Business_Process_Data>
        <bsvc:Comment>Approved after verifying cost center budget.</bsvc:Comment>
      </bsvc:Approve_Business_Process_Data>
    </bsvc:Approve_Business_Process_Request>
  </soapenv:Body>
</soapenv:Envelope>
```

### SOAP `Send_Back_Business_Process` Example

Note that SOAP `Send_Back_Business_Process` takes the `Business_Process_Step_ID` Reference ID (for example, from `Workflow_Step_ID` on the business process definition) rather than the runtime `Event Record` WID:

xml

```
<bsvc:Send_Back_Business_Process_Request bsvc:version="v43.0">
  <bsvc:Event_Reference>
    <bsvc:ID bsvc:type="WID">f1208b90446c11de98360015c5e6daf6</bsvc:ID>
  </bsvc:Event_Reference>
  <bsvc:Send_Back_Business_Process_Data>
    <bsvc:Business_Process_Step_ID>REQUEST_TIME_OFF_INITIATION</bsvc:Business_Process_Step_ID>
    <bsvc:Comment>Adjust hours on Friday from 8 to 4 to match half-day holiday schedule.</bsvc:Comment>
  </bsvc:Send_Back_Business_Process_Data>
</bsvc:Send_Back_Business_Process_Request>
```

Also note embedded `Business_Process_Parameters` on domain-initiating SOAP operations (such as `Enter_Time_Off` in `Absence_Management`, `Submit_Expense_Report` or `Submit_Requisition` in `Resource_Management`, and `Change_Job` in `Staffing`): setting `<bsvc:Auto_Complete>true</bsvc:Auto_Complete>` bypasses downstream approvals **only** when called by an authorized integration security group during data loads or pre-approved system syncs. Never enable `Auto_Complete` on employee self-service submissions, or you will skip manager approval chains completely.

## Comment Sync Rules and Common Validation Errors (`400` / `Validation_Fault`)

Workday’s comment configuration trips up API callers because **Disable Comments** exists in two places—globally on **`Edit Tenant Setup - Business Processes`** and locally on each **Business Process Security Policy**:

-   **Actions Exempt from `Disable Comments`:** Even when `Disable Comments` is checked, Workday **still** accepts (and requires) reasons on *Deny*, *Send Back*, *Cancel*, *Rescind*, *Correct*, *Manual Advance*, and *Add Approvers*.
-   **Approvals Under `Disable Comments`:** On *Approve* and *To Do* steps, if `Disable Comments` is active (globally synced or locally overridden on the Business Process Security Policy), sending a `comment` string returns error **`A1573`** (`You can't comment on this business process type`) in REST or a `Validation_Fault` in SOAP (`This Business Process has been configured to disable comment`). Conversely, when comments are enabled, omitting `comment` on REST `/approve` or `/deny` returns **`A181`**.

| Error Code / SOAP Fault | Exact Meaning & Root Cause | Fix |
| --- | --- | --- |
|  **`A181`** (`Specify a comment` / `A comment is required`) | REST `/approve` or `/deny` body omitted `comment` on a BP where comments are enabled. | Pass a non-empty `comment` string in the JSON request body. |
|  **`A1573`** (`You can't comment on this business process type`) | `Disable Comments` is enabled on `Edit Tenant Setup - Business Processes` or the BP Security Policy. | Omit `comment` for that business process type or uncheck `Disable Comments` on the BP Security Policy. |
|  **`A190`** (`This event step type cannot be approved`) | Caller sent `/approve` to a `To Do`, `Questionnaire`, or `Action` step. | Inspect `stepType` on `GET /eventSteps/{ID}` and route `To Do` steps to `/toDo`. |
|  **`A183` / `A225`** (`Cannot be denied` / `Not authorized to deny`) | Step type does not support denial, or caller’s security group is absent from **Who Can Deny** on the BP Security Policy. | Verify **Deny** permissions on `Business Process Policy > Edit` or offer **Send Back** instead. |
|  **`A212`** (`This event step is not awaiting your action`) | Wrong WID passed (such as parent `Event` WID), step already completed by another approver, or caller lacks assignment/delegation. | Pass the `Event Record` WID and refresh queue state gracefully on `A212`. |
|  **`A202` / `A227`** (`Step sending back to/from isn't supported`) | Target step in `to.id` is not a valid prior step, or **Send Back** is disallowed on this step. | Populate valid destinations dynamically from `GET /values/sendBack/to/`. |
|  **SOAP: `This task has been delegated to another user and cannot be Denied`** | Delegator unchecked `Retain Access to Delegated Tasks within My Tasks` when delegating. | Have the active delegate act on the step, or update delegation retention settings. |

When building external approval screens with [Kiweely Leaf](https://kiweely.com/leaf) or connecting AI assistants through [Kiweely Bridge](https://kiweely.com/bridge) (**both coming next**), each approval or send-back executes under the signed-in manager’s own Workday OAuth session—preserving every Business Process Security Policy check and recording the human approver in Workday’s [process audit history](https://kiweely.com/guides/workday-business-process-audit-trail-initiated-via-web-service).

## Frequently asked questions

### What ID does POST /businessProcess/v1/eventSteps/{ID}/approve expect in the URL path?

It expects the 32-character lowercase hexadecimal Workday ID (WID) of the awaiting Event Record (the individual business process step returned by GET /common/v1/workers/me/inboxTasks or GET /businessProcess/v1/eventSteps), not the WID of the parent Event.

### Why does SOAP Approve\_Business\_Process take an Event\_Reference while REST /eventSteps/{ID}/approve takes an Event Record WID?

The legacy Integrations SOAP operations (Approve\_Business\_Process, Deny\_Business\_Process, Send\_Back\_Business\_Process) target the parent Event\_Reference and advance the step awaiting the caller, whereas the modern businessProcess v1 REST API addresses the exact Event Record step resource directly—avoiding ambiguity when an event has parallel in-progress steps.

### Is a comment required when approving or denying a step through the Workday REST API?

In businessProcess v1 REST, both /approve and /deny validate that a comment field is provided (returning HTTP 400 error A181 if omitted), unless comments are disabled on Edit Tenant Setup - Business Processes or the Business Process Security Policy (which returns A1573 if a comment is sent).

### How do I complete a To Do step instead of an Approval step via REST?

Calling /approve on a To Do step fails with error A190 ('This event step type cannot be approved'). Instead, call POST /businessProcess/v1/eventSteps/{ID}/toDo with stepAction set to { id: '133d5c88baa64136aab041c1d2e9ed53' } for Submit.

## Sources checked

-   [Concept: Manage a Worker's My Tasks Items](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/manage-business-processes/dan1370796639881.html)
-   [Reference: Edit Tenant Setup - Business Processes](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/tenant-setup/dan1370796487589.html)
-   [Concept: Bulk Approve Business Processes](https://doc.workday.com/admin-guide/en-us/manage-workday/business-processes/manage-business-processes/mcc1590008202670.html)
-   [Workday API Reference Overview](https://developer.workday.com/apis)

## Related guides

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

-   [### Querying Pending Workday My Tasks and Inbox Approvals via API and WQL Retrieve pending Workday My Tasks items for the signed-in worker via GET /common/v1/workers/{ID}/inboxTasks, or query awaiting approvals with WQL data sources such as businessProcessTransactionsAwaitingMyAction and businessProcessStepsAwaitingMe alongside businessProcess v1 REST calls.](https://kiweely.com/guides/workday-inbox-my-tasks-awaiting-action-rest-wql)
-   [### 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)
-   [### Workday Awaiting Action: who is the step waiting on, and how do you move it? Awaiting Action means a step is waiting for someone to act, and a day or more is normal. Open Business Process > Full Process Record to see who, then have them finish it in My Tasks, or reassign, delegate or manually advance the step.](https://kiweely.com/guides/business-process-awaiting-action)

### More guides on Integrations and APIs

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

-   [How Workday Studio PutIntegrationMessage Severity Levels Control Completed-with-Warnings vs. Aborted Runs](https://kiweely.com/guides/workday-studio-error-severity-critical-warning-abort)
-   [How to Fix Workday Studio SDKProfile Not Current and Unsigned Software Startup Errors on Mac and Windows](https://kiweely.com/guides/workday-studio-sdkprofile-not-current-unsigned-macos-errors)
-   [How to Authenticate Workday Studio and External Tools Using an OAuth API Client with PKCE (When SSO Blocks Passwords)](https://kiweely.com/guides/workday-api-client-pkce-sso-without-workday-password)
-   [Workday PECI vs. PICOF Payroll Connectors: How Effective-Dated Stack and Retro Changes Export](https://kiweely.com/guides/workday-peci-picof-payroll-connector-change-detection)
-   [Why does my Workday Accounting Journal EIB fail? Balancing, worktag and period errors](https://kiweely.com/guides/workday-financials-accounting-journal-eib-validation-errors)
-   [How to Find Every Domain and Web Service Permission an ISU Needs in Workday (Without Guesswork)](https://kiweely.com/guides/workday-isu-permissions-activate-pending-security-policy-changes)
-   [How to Fix The Load Contains a Duplicate Key and Invalid Reference ID Errors in Workday EIB](https://kiweely.com/guides/workday-eib-duplicate-key-reference-id-errors)
-   [How to Troubleshoot Workday Cloud Connect for Benefits (CCB) and Missing Dependents on 834 Feeds](https://kiweely.com/guides/workday-cloud-connect-for-benefits-834-errors)

### From the blog on Integrations and APIs

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

-   [Untangling Inherited Workday Studio Integrations: A Practical Modernization Playbook](https://kiweely.com/blog/untangling-inherited-workday-studio-integrations)
-   [Why Most Workday Studio Integrations Ship Without Tests](https://kiweely.com/blog/workday-studio-integrations-without-tests)
-   [The Slow Change Cycle in Workday Studio (and How to Break It)](https://kiweely.com/blog/workday-studio-slow-change-cycle)

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