Position Tree Nodes List of Values
positionTreeNodesLOV Based on latest (2026.09)
Look up the list of values for Position Tree Nodes.
The record key positionTreeNodesLOVUniqID is a generated hash. Take it from the record's links (rel self) in a GET response; never build it yourself.
Oracle documents an Effective-Of header and an effectiveDate parameter for this resource, used for date-effective reads and changes.
- Operations
- GET (list)GET (one)
- Record key
positionTreeNodesLOVUniqID- Required on create
- no create on this resource
- At a glance
- 7 fields1 finders0 children
- Extra parameters
?effectiveDate=Effective-Of:
Try it
Only attributes Oracle marks as searchable are offered.
GET /hcmRestApi/resources/11.13.18.05/positionTreeNodesLOV?fields=EffectiveEndDate,EffectiveStartDate,ParentPositionId,ParentPositionName,PositionId&limit=25&onlyData=true
{
"items": [
{
"EffectiveEndDate": "2026-01-31",
"EffectiveStartDate": "2026-01-31",
"ParentPositionId": 0,
"ParentPositionName": "<string, max 240>",
"PositionId": 0
}
],
"count": 25,
"hasMore": true,
"limit": 25,
"offset": 0
}Shapes and placeholders, not real data. Replace https://<your-pod> and the login with your own: this site never sees them. Based on Oracle's latest (2026.09) REST specification.
Fields 7
| Attribute | Type | Use |
|---|---|---|
EffectiveEndDate | date | Read-onlySearchable |
EffectiveStartDate | date | Read-onlySearchable |
ParentPositionId | number | Read-onlySearchable |
ParentPositionName | text · max 240 | Read-onlySearchable |
PositionId | number | Read-onlySearchable |
PositionName | text · max 240 | Read-onlySearchable |
TreeNodeId | text · max 32 | Read-onlySearchable |
Names, types, labels and flags from Oracle's REST specification (latest (2026.09)). Flexfield and custom attributes vary by pod: check /describe for yours.
Finders 1
Predefined searches: ?finder=Name;variable=value,variable2=value2. Pick one in Try it to build the call.
findByWord·FilterAttributesSearchTermsSysEffectiveDateTreeVersionId
Check a payload
Checked in your browser only; nothing you paste is sent anywhere. Checks names and flags, not values.
Use in AI Agent Studio
- Point a Business Object or REST tool at
/hcmRestApi/resources/11.13.18.05/positionTreeNodesLOVand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
findByWordfor the agent's main search: its variables become clean tool parameters. - Narrow with
q=on searchable fields and a smalllimit; for a count usetotalResults=true&limit=1. - Call once and pass the result on to later steps rather than calling the same endpoint again.
More in For Builders.
Pitfalls
- Attribute names are case-sensitive in
q,fieldsand bodies:EffectiveEndDate, noteffectiveenddate. onlyData=trueremoveslinks, and this resource's key only comes fromlinks. Leave it off when you need the key.- Send dates as
YYYY-MM-DD; date-time fields take ISO 8601 with a time zone. - A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.