Positions List of Values V2
positionsLovV2 Based on latest (2026.09)
Look up the list of values for PositionsV2.
The record key positionsLovV2UniqID is a generated hash. Take it from the record's links (rel self) in a GET response; never build it yourself.
- Operations
- GET (list)GET (one)
- Record key
positionsLovV2UniqID- Required on create
- no create on this resource
- At a glance
- 22 fields3 finders0 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /hcmRestApi/resources/11.13.18.05/positionsLovV2?fields=BusinessUnitId,BusinessUnitName,DepartmentId,DepartmentName,DisplayName&limit=25&onlyData=true
{
"items": [
{
"BusinessUnitId": 0,
"BusinessUnitName": "<string>",
"DepartmentId": 0,
"DepartmentName": "<string>",
"DisplayName": "<string>"
}
],
"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 22
| Attribute | Type | Use |
|---|---|---|
BusinessUnitId | number | Searchable |
BusinessUnitName | text | Searchable |
DepartmentId | number | Searchable |
DepartmentName | text | Searchable |
DisplayName | text | Searchable |
EffectiveEndDate | date | Searchable |
EffectiveStartDate | date | Searchable |
FullName | text | Searchable |
HiringStatus | text | Searchable |
JobCode | text | Searchable |
JobId | number | Searchable |
JobName | text | Searchable |
LocationCode | text | Searchable |
LocationId | number | Searchable |
LocationName | text | Searchable |
ParentPositionCode | text | Searchable |
ParentPositionId | number | Searchable |
ParentPositionName | text | Searchable |
PersonNumber | text | Searchable |
PositionCode | text | Searchable |
PositionId | number | Searchable |
PositionName | text | Searchable |
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 3
Predefined searches: ?finder=Name;variable=value,variable2=value2. Pick one in Try it to build the call.
findByPositionId·ActiveStatusEffectiveDatePositionIdfindByWord·ActiveStatusBusinessGroupIdBusinessUnitIdEffectiveDateFilterAttributesHiringStatusListOfPositionIdSearchTermsTypeCodefindMultiplePositionsById·EffectiveDateListOfPositionId
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/positionsLovV2and ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
findByPositionIdfor 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:BusinessUnitId, notbusinessunitid. 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.