Get a worker phone
get
/hcmRestApi/resources/11.13.18.05/workers/{workersUniqID}/child/phones/{PhoneId}
Request
Path Parameters
-
PhoneId(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=
-
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.
Query Parameters
-
dependency: string
This parameter specifies dependencies which are fields that are set before and rolled back after generating the response. Generally they are used to preview the effects of an attribute change. The fields specified in this parameter are always set in the resource instance in question. When a child resource collection is requested and the parameter is set, the fields will be set in the parent resource instance before generating the resource collection payload. The value of this query parameter is a set of dependency fields. Example: dependency=ProductId=2
Format: <attr1>=<val1>,<attr2>=<value2> -
expand: string
When this parameter is provided, the specified children are included in the resource payload (instead of just a link). The value of this query parameter is "all" or "". More than one child can be specified using comma as a separator. Example: ?expand=Employees,Localizations. Nested children can also be provided following the format "Child.NestedChild" (Example: ?expand=Employees.Managers). If a nested child is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?expand=Employees.Managers" is the same as "?expand=Employees,Employees.Managers" (which will expand Employees and Managers).
-
fields: string
This parameter filters the resource fields. Only the specified fields are returned, which means that if no fields are specified, no fields are returned (useful to get only the links). If an indirect child resource is provided (Example: Employees.Managers), the missing children will be processed implicitly. For example, "?fields=Employees.Managers:Empname" is the same as "?fields=;Employees:;Employees.Managers:Empname" (which will only return the "Empname" field for Managers). the value of this query parameter is a list of resource fields. The attribute can be a direct (Example: Employees) or indirect (Example: Employees.Managers) child. It cannot be combined with expand query parameter. If both are provided, only fields will be considered.
Format: ?fields=Attribute1,Attribute2
Format for fields in child resource: ?fields=Accessor1:Attribute1,Attribute2 -
links: string
This parameter can be used to show only certain links while accessing a singular resource or a resource collection. The parameter value format is a comma-separated list of : <link_relation>
Example:
self,canonical -
onlyData: boolean
The resource item payload will be filtered in order to contain only data (no links section, for example).
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.
There's no request body for this operation.
Back to TopResponse
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 retrieve a worker phone by submitting a GET 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 GET "https://<host>:<port>/hcmRestApi/resources/11.13.18.05/workers/00020000000EACED0005770800005AF3116303090000004AACED00057372000D6A6176612E73716C2E4461746514FA46683F3566970200007872000E6A6176612E7574696C2E44617465686A81014B597419030000787077080000016ABDF0400078/child/phones/300100187109511"
Example of Response Header
The following is an example of the response header.
Status: HTTP/1.1 200 OK 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": [
{...
}
]
}