Create a worker phone
post
/hcmRestApi/resources/11.13.18.05/workers/{workersUniqID}/child/phones
Request
Path Parameters
-
workersUniqID(required): string
This is the hash key of the attributes which make up the composite key for the Workers resource and used to uniquely identify an instance of Workers. The client should not generate the hash key value. Instead, the client should query on the Workers collection resource in order to navigate to a specific instance of Workers 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.
-
Upsert-Mode:
Contains one of the following values: true or false. If true, the server performs an Upsert operation instead of a Create operation. During an Upsert operation, the server attempts to find an existing resource that matches the payload. If a match is found, the server updates the existing resource instead of creating a new one. If not found or false (default), the server performs a Create operation. Note that the Upsert operation isn't supported for date-effective REST resources.
Supported Media Types
- application/json
Root Schema : schema
Type:
Show Source
object-
AreaCode: string
Title:
Area CodeMaximum Length:30Area code of the phone number. -
CountryCodeNumber: string
Title:
Country CodeMaximum Length:30Country code of the phone number. Valid values are defined in the hcmCountriesLov. -
Extension: string
Title:
ExtensionMaximum Length:60Extension number for the phone. -
FromDate: string
(date)
Title:
From DateDate from when the phone number is valid. -
LegislationCode: string
Title:
CountryMaximum Length:4Phone legislation code. -
PhoneNumber(required): string
Title:
NumberMaximum Length:60Phone number of various phone types such as Work, Home, and so on. -
phonesDFF: array
phonesDFF
-
PhoneType(required): string
Title:
TypeMaximum Length:30Type of phone such as Work, Home, and so on. Valid values are defined in the commonLookupsLOV. -
PrimaryFlag: boolean
Title:
PrimaryMaximum Length:255Indicates whether the phone number is the primary phone of the worker. -
ToDate: string
(date)
Title:
To DateDate until when the phone number is valid. -
Validity: string
Title:
ValidityMaximum Length:30Time of day when a person can be reached at a specific phone number.
Nested Schema : workers-phones-phonesDFF-item-post-request
Type:
Show Source
object-
__FLEX_Context: string
Title:
Context ValueMaximum Length:30 -
__FLEX_Context_DisplayValue: string
Title:
Context Value -
PhoneId: integer
(int64)
Title:
Phone ID
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 : workers-phones-item-response
Type:
Show Source
object-
AreaCode: string
Title:
Area CodeMaximum Length:30Area code of the phone number. -
CountryCodeNumber: string
Title:
Country CodeMaximum Length:30Country code of the phone number. Valid values are defined in the hcmCountriesLov. -
CreatedBy: string
Title:
Created ByRead Only:trueMaximum Length:64User who created the phone information. -
CreationDate: string
(date-time)
Title:
Creation DateRead Only:trueDate and time when the phone information was created. -
Extension: string
Title:
ExtensionMaximum Length:60Extension number for the phone. -
FromDate: string
(date)
Title:
From DateDate from when the phone number is valid. -
LastUpdateDate: string
(date-time)
Title:
Last Updated DateRead Only:trueDate and time when the phone information was last updated. -
LastUpdatedBy: string
Title:
Last Updated ByRead Only:trueMaximum Length:64User who last updated the phone information. -
LegislationCode: string
Title:
CountryMaximum Length:4Phone legislation code. -
LegislationName: string
Title:
CountryRead Only:trueMaximum Length:80Name of the person's legislation. -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
PhoneId: integer
(int64)
Title:
Phone IDRead Only:trueSurrogate identifier for the phone. -
PhoneNumber: string
Title:
NumberMaximum Length:60Phone number of various phone types such as Work, Home, and so on. -
phonesDFF: array
phonesDFF
-
PhoneType: string
Title:
TypeMaximum Length:30Type of phone such as Work, Home, and so on. Valid values are defined in the commonLookupsLOV. -
PhoneTypeMeaning: string
Title:
TypeRead Only:trueMaximum Length:80Meaning of the person's phone type. -
PrimaryFlag: boolean
Title:
PrimaryMaximum Length:255Indicates whether the phone number is the primary phone of the worker. -
ToDate: string
(date)
Title:
To DateDate until when the phone number is valid. -
Validity: string
Title:
ValidityMaximum Length:30Time of day when a person can be reached at a specific phone number. -
ValidityMeaning: string
Title:
ValidityRead Only:trueMaximum Length:80Description of the phone validity. Valid values are defined in the commonLookupsLOV.
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Nested Schema : link
Type:
Show Source
object-
href: string
Title:
hyperlink referenceThe URI to the related resource. -
kind: string
Title:
kindAllowed Values:[ "collection", "item", "describe", "other" ]The kind of the related resource. -
name: string
Title:
nameThe name of the link to the related resource. -
properties: object
properties
-
rel: string
Title:
relationAllowed 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.
Nested Schema : workers-phones-phonesDFF-item-response
Type:
Show Source
object-
__FLEX_Context: string
Title:
Context ValueMaximum Length:30 -
__FLEX_Context_DisplayValue: string
Title:
Context Value -
links: array
Links
Title:
LinksThe link relations associated with the resource instance. -
PhoneId: integer
(int64)
Title:
Phone ID
Nested Schema : Links
Type:
arrayTitle:
LinksThe link relations associated with the resource instance.
Show Source
Links
- legislationCodesLov
-
The hcmCountriesLov resource includes the list of values for countries.
- phoneTypesLov
-
Parameters:
- finder:
LegislationCodeFinder%3BLookupCode%3D{PhoneType}%2CLookupType%3DPHONE_TYPE%2CLegislationCode%3D{LegislationCode}
The common lookups list of values resource is used to query the list of values of common lookups, which are legacy lookups or lookups that have attributes. Common lookups are defined in the common lookup view and support backward compatibility. - finder:
- phonesDFF
-
Operation: /hcmRestApi/resources/11.13.18.05/workers/{workersUniqID}/child/phones/{PhoneId}/child/phonesDFFParameters:
- PhoneId:
$request.path.PhoneId - workersUniqID:
$request.path.workersUniqID
- PhoneId:
- validityLovVA
-
Parameters:
- finder:
LegislationCodeFinder%3BLookupCode%3D{Validity}%2CLookupType%3DPER_CONTACT_TIMES%2CLegislationCode%3D{LegislationCode}
The common lookups list of values resource is used to query the list of values of common lookups, which are legacy lookups or lookups that have attributes. Common lookups are defined in the common lookup view and support backward compatibility. - finder:
Examples
The following example shows how to create a worker phone by submitting a POST request on the REST resource using cURL.
curl -i -u "<username>:<password>" -H "Content-Type: application/vnd.oracle.adf.resourceitem+json" -H "REST-Framework-Version: 4" -X POST -d <payload> "https://<host>:<port>/hcmRestApi/resources/11.13.18.05/workers/00020000000EACED0005770800005AF3116303090000004AACED00057372000D6A6176612E73716C2E4461746514FA46683F3566970200007872000E6A6176612E7574696C2E44617465686A81014B597419030000787077080000016ABDF0400078/child/phones
Example of Payload
The following is an example of the payload.
{
"PhoneType": "H1",
"PhoneNumber": "7543010"
}
Example of Response Header
The following is an example of the response header.
Status: HTTP/1.1 201 Created Content-Type : application/vnd.oracle.adf.resourceitem+json
Example of Response Body
The following example shows the contents of the response body in JSON format.
{
"PhoneId": 300100187109511,
"PhoneType": "H1",
"LegislationCode": "LR",
"CountryCodeNumber": "231",
"AreaCode": null,
"PhoneNumber": "7543010",
"Extension": null,
"FromDate": "2019-05-16",
"ToDate": null,
"CreatedBy": "VMOSS",
"CreationDate": "2019-05-16T12:14:49+00:00",
"LastUpdatedBy": "VMOSS",
"LastUpdateDate": "2019-05-16T12:14:49.972+00:00",
"PrimaryFlag": true,
"links": [
{...
}
]
}