---
category: [Administration & Integrations, Administration & Integrations/Workday API, Platform and Product Extensions, Platform and Product Extensions/Integration]
nav: wcp_docs
parent_url: /wcp_docs/
title: >- 
  Reference: Workers/Job Changes
layout: subsection
---

## <a id="conref_common_service_urlBasePath"></a>URL Base Path

<b>Workday API Gateway Base Path</b>

For REST API calls in Workday Extend and Orchestrate for Integrations, use the regional API Gateway base URL for your account. See [Reference: Workday Extend API Gateways and Authorization Base URLs](https://developer.workday.com/documentation/dlh1653340161856) on the Developer Site. Note that the API Gateway base URL doesn’t include the tenant name.

<b>Tenant Base Path</b>

For traditional Integrations using tenanted REST APIs calls:

```
https://<hostname>/api/common/<version>/<tenant>
```

Example:

```
https://yourTenantHostName.com/api/common/v1/gms
```

## <a id="refsyn_N10019_N10016_N10001"></a>URI

Collection of Job Changes for a Worker:

```
/workers/{id}/jobChanges
```

<b>URI Parameters</b>

<table><thead><tr><th>URI Parameter</th><th>Description</th></tr></thead><tbody><tr><td>id</td><td>A reference to a worker. Example: Worker WID.</td></tr></tbody></table><br/>

## <a id="section_N10050_N10016_N10001"></a>Description

Workers/Job Changes resource represents job changes for a specific worker. You can only view the worker and job changes information permitted by the security profile of the current user.

Workers/Job Changes resource supports this method:

-   [POST Workers/Job Changes](/wcp_docs/dan1370797990026.html#POST)


## <a id="POST"></a>POST Workers/Job Changes

-   <b>Secured by:</b>

    Change Job



Use this method to initiate a job change for the specified worker.

You supply a JSON format body with your request. In the request body, supply values for these parameters:

<table><thead><tr><th>Body Parameter</th><th>Type</th><th>Description</th></tr></thead><tbody><tr><td>jobChangeReason</td><td>id</td><td>Reason for the job change. Use the Job Change Reasons resource to get the IDs for job change reasons.</td></tr><tr><td>supervisoryOrganization</td><td>id</td><td>Target organization for the job change. The worker is in this organization after the job change is complete. Use the Supervisory Organizations resource to get the IDs for supervisory organizations.</td></tr><tr><td>effective</td><td>date</td><td>(Optional) Effective date of the job change. If left blank, is set to current date.</td></tr><tr><td>moveManagersTeam</td><td>boolean</td><td>(Optional) If the manager team is transferred to the new organization.</td></tr><tr><td>proposedOrganizations</td><td>organizations</td><td>(Optional) Set of proposed organizations, which are the organizations to which the worker is assigned.</td></tr></tbody></table><br/>

To find valid values for jobChangeReason, and supervisoryOrganization, use the Job Change and the Supervisory Organizations resources.

The proposed organizations are the organizations to which the worker is assigned. To change the proposed organizations, you supply:

-   All proposed organizations that you want to set for the worker in the request body, including the unchanged organizations. Even if you only want to change one proposed organization, you supply all organizations that are to be set for the worker. If you do not include a proposed organization, then that organization will not be set for the worker.
-   Worker proposed organizations, which are the organizations to which the worker is assigned. The organization WIDs exist in Workday.
-   Worker supervisory organization. A supervisory organization groups workers into a management hierarchy. The organization WID exists in Workday.


<b>Note:</b> To change the proposed organizations, you enable the <i>Change Organization Assignments</i> step in the <i>Change Job</i> business process. When a request contains proposed organizations, an <i>Assign Organizations</i> event is created after Workday validates the request. The <i>Assign Organizations</i> event is processed in addition to the <i>Change Job</i> event.

The <i>Change Job</i> business process has restrictions. You might receive an error message when you attempt to complete a job change:

<table><thead><tr><th>HTTP Response Code</th><th>Error Message</th><th>Description/Solution</th></tr></thead><tbody><tr><td>400</td><td>Worker has additional jobs. This task is not supported for workers with multiple jobs.</td><td> </td></tr><tr><td>400</td><td>Reason is required.</td><td>Supply a value for jobChangeReason.</td></tr><tr><td>400</td><td>Proposed Supervisory Organization is required.</td><td>Supply a value for supervisoryOrganization.</td></tr><tr><td>400</td><td>You cannot initiate this action because there are other pending actions for the worker that conflict with this one. Close any pending Staffing, Matrix Organization, Pay Group or Organization events before initiating this action.</td><td> </td></tr><tr><td>400</td><td>Reason is not valid for the Job Change Event or the processing user is a Manager and the Reason is not valid for managers.</td><td> </td></tr><tr><td>400</td><td>Reason is not valid for the worker type (Employee or Contingent Worker).</td><td> </td></tr><tr><td>400</td><td>The proposed supervisory organization is in a Hiring Freeze. It cannot be selected.</td><td> </td></tr><tr><td>400</td><td>Supervisory Organization must be active.</td><td> </td></tr><tr><td>400</td><td>The hiring restrictions for the proposed supervisory organization do not allow this type of worker.</td><td> </td></tr><tr><td>400</td><td>The Proposed Supervisory Organization must be different from the Position's current organization when the reason has a category of Transfer.</td><td> </td></tr><tr><td>400</td><td>Organization is not accessible by the user.</td><td> </td></tr><tr><td>400</td><td>Proposed supervisory organization is not valid. It will be made inactive after the event effective date. This will result in this position not having a supervisory organization.</td><td> </td></tr><tr><td>400</td><td>Worker is terminated and does not have a future hire.</td><td> </td></tr><tr><td>400</td><td>Worker submitted is the processing user.</td><td> </td></tr><tr><td>400</td><td>This position is in a pending Merit Event. The effective date must be after the pending Merit Event's effective date.</td><td> </td></tr><tr><td>400</td><td>The current position has a pending organization change or a completed Supervisory Organization change effective after this date. Therefore, this position cannot have changes as of the effective date.</td><td> </td></tr><tr><td>400</td><td>The effective date must be after the date of the last completed Change Organization assignment.</td><td> </td></tr><tr><td>400</td><td>The effective date must be equal to or greater than the date the position was last updated.</td><td> </td></tr><tr><td>400</td><td>The effective date must be after the date of the last completed Assign Pay Group change.</td><td> </td></tr><tr><td>400</td><td>The effective date must be after the date of the last completed Matrix Organization change.</td><td> </td></tr><tr><td>400</td><td>Hiring restrictions are missing for the organization selected.</td><td> </td></tr><tr><td>400</td><td>The date entered cannot be earlier than the earliest hire date.</td><td> </td></tr><tr><td>400</td><td>Proposed Organizations have Organization Types that cannot be part of Change Organization Assignments.</td><td>Supply valid organizations in the proposed organizations list. Organizations with these Organization Types are required: Company, Cost Center, Region.</td></tr></tbody></table><br/>

## <a id="section_N10305_N10016_N10001"></a>POST Workers/Job Changes Examples

This POST request transfers Dana Marek (id=fac08217aeca474fad96d5f3771e76bc) to a new supervisory organization.

```
POST /workers/fac08217aeca474fad96d5f3771e76bc/jobChanges
```

using this request body:

```
{ 
     "jobChangeReason" : {"id":"b7187dceedb34c8db3a8e15adf02a620"},
     "supervisoryOrganization" : {"id":"fd935c1ac1a047f8a11c74add2991e04"}
}
```

The response body is the job change process in JSON format:

```
{
   "descriptor": "Transfer: Dana Marek",
   "id": "3e6318cff9fd495bae0b44d40525509b",
   "href": "https://{Workday REST API Endpoint}/businessProcesses/3e6318cff9fd495bae0b44d40525509b"
}
```

This POST request for John Smith (id=e6dc3990e66242d2b9308d165d7c0e21) sets their proposed organizations, which are the organizations to which John is assigned:

```
POST /workers/e6dc3990e66242d2b9308d165d7c0e21/jobChanges
```

Request body:

```
{
     "jobChangeReason":{"id":"3e420aee42f04791a07cfc18cf6f154f"},
     "supervisoryOrganization":{"id":"8a30f8b5b65e4a48b01d4e17ec8f8778"},
     "proposedOrganizations":
     [
          {"id":"6f806d33769347b69088d4bb3b538d77"}, 
          {"id":"211359ad55e641adbb806f5392414c15"},
          {"id":"d93bd712c6a44ac297c4ed37ac6b83c1"}
     ]
}
```

The response body is the job change process in JSON format:

```
{
  "descriptor": "Data Change: John Smith",
  "id": "ff3c57e0cb6710001d55e45fc76bf1d6",
  "href": "https://{Workday REST API Endpoint}/businessProcesses/ff3c57e0cb6710001d55e45fc76bf1d6",
  "jobChangeReason": {
    "descriptor": "Data Change > Data Change > Change Details of Job",
    "id": "3e420aee42f04791a07cfc18cf6f154f",
    "href": "https://{Workday REST API Endpoint}/jobChangeReasons/3e420aee42f04791a07cfc18cf6f154f"
  },
  "moveManagersTeam": false,
  "proposedOrganizations": [
    {
      "descriptor": "Company 24",
      "id": "6f806d33769347b69088d4bb3b538d77"
    },
    {
      "descriptor": "Cost Center 9",
      "id": "211359ad55e641adbb806f5392414c15"
    },
    {
      "descriptor": "Region 13",
      "id": "d93bd712c6a44ac297c4ed37ac6b83c1"
    }
  ],
  "supervisoryOrganization": {
    "descriptor": "Supervisory Organization 2",
    "id": "8a30f8b5b65e4a48b01d4e17ec8f8778",
    "href": "https://{Workday REST API Endpoint}/supervisoryOrganizations/8a30f8b5b65e4a48b01d4e17ec8f8778"
  }
}
```