Action to move a job application to a specific phase and state
post
/hcmRestApi/resources/11.13.18.05/recruitingJobApplications/{JobApplicationId}/action/move
Allows a member of the hiring team to move an application to a specific phase and state.
Request
Path Parameters
-
JobApplicationId(required): integer(int64)
The value of this parameter could be a hash of the key that is used to uniquely identify the resource item. The client should not generate the hash key value. Instead, the client should query on the collection resource with a filter to navigate to a specific resource item. For example: products?q=InventoryItemId=
Header Parameters
-
Metadata-Context:
If the REST API supports runtime customizations, the shape of the service may change during runtime. The REST client may isolate itself from these changes or choose to interact with the latest version of the API by specifying this header. For example: Metadata-Context:sandbox="TrackEmployeeFeature".
-
REST-Framework-Version:
The protocol version between a REST client and service. If the client does not specify this header in the request the server will pick a default version for the API.
Supported Media Types
- application/vnd.oracle.adf.action+json
Root Schema : schema
Type:
Show Source
object
-
comments: string
Contains comments about the move of the job application
-
phaseId: number
Unique ID assigned to each target phase to move the job application to
-
reasonId: number
Unique ID assigned to each reason why the job application was moved
-
stateId: number
Unique ID assigned to each target state to move the job application to
Response
Default Response
The following table describes the default response for this task.