Submit all recruiting job requisitions other languages
post
/hcmRestApi/resources/11.13.18.05/recruitingJobRequisitions/{recruitingJobRequisitionsUniqID}/child/otherLocations
Request
Path Parameters
-
recruitingJobRequisitionsUniqID(required): string
This is the hash key of the attributes which make up the composite key for the Recruiting Job Requisitions resource and used to uniquely identify an instance of Recruiting Job Requisitions. The client should not generate the hash key value. Instead, the client should query on the Recruiting Job Requisitions collection resource in order to navigate to a specific instance of Recruiting Job Requisitions to get the hash key.
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/json
Root Schema : schema
Type:
Show Source
object
-
GeographyNodeId: integer
(int64)
Title:
Other Locations
Geography Node ID in recruiting job requisitions other locations. -
LocationId: integer
(int64)
Location ID in recruiting job requisitions other locations.
Response
Supported Media Types
- application/json
Default Response
The following table describes the default response for this task.
Headers
-
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.
Root Schema : recruitingJobRequisitions-otherLocations-item-response
Type:
Show Source
object
-
CreatedBy: string
Title:
Created By
Read Only:true
Maximum Length:64
Requisition created for other locations. -
CreationDate: string
(date-time)
Title:
Creation Date
Read Only:true
Creation Date in recruiting job requisitions other locations. -
GeographyNodeId: integer
(int64)
Title:
Other Locations
Geography Node ID in recruiting job requisitions other locations. -
LastUpdateDate: string
(date-time)
Title:
Last Updated Date
Read Only:true
Last Update Date in recruiting job requisitions other locations. -
LastUpdatedBy: string
Title:
Last Updated By
Read Only:true
Maximum Length:64
Last Update using in recruiting job requisitions other locations. -
links: array
Links
Title:
Links
The link relations associated with the resource instance. -
LocationId: integer
(int64)
Location ID in recruiting job requisitions other locations.
Nested Schema : Links
Type:
array
Title:
Links
The link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object
-
href: string
Title:
hyperlink reference
The URI to the related resource. -
kind: string
Title:
kind
Allowed Values:[ "collection", "item", "describe", "other" ]
The kind of the related resource. -
name: string
Title:
name
The name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relation
Allowed Values:[ "self", "lov", "parent", "canonical", "child", "enclosure", "action", "custom" ]
The name of the relation to the resource instance. Example: self.
Nested Schema : properties
Type:
Show Source
object
-
changeIndicator: string
Change indicator or the ETag value of the resource instance.
Links
- geographyHierarchyLocationsLOV
-
The following properties are defined on the LOV link relation:
- Source Attribute: GeographyNodeId; Target Attribute: GeographyNodeId
- Display Attribute: GeographyNodeId
Examples
The following example shows how to create an other location for a job requisition by submitting a POST request on the REST resource using cURL.
curl -i -u "<username>:<password>" -X POST -d payload http://host:port/hcmCoreApi/resources/11.13.18.05/recruitingJobRequisitions/PR_REQ_501/child/otherLocations
Example of Payload
The following is an example of the payload.
{ "GeographyNodeId": 300100171497454 }
Example of Response Header
The following is an example of the response header.
HTTP/1.1 200 OK Content-Type : application/octet-stream
Example of Response Body
The following example shows the contents of the response body in JSON format.
{ "WorkLocationId": 300100175010395, "LocationId": 16306, "CreatedBy": "TM-MFITZIMMONS", "CreationDate": "2019-02-25T16:10:36-08:00", "LastUpdatedBy": "TM-MFITZIMMONS", "LastUpdateDate": "2019-02-25T16:10:36.537-08:00", "links": [4] {... ...} }