// fusionrest agent · hcm · list of values
Recruiting Locations LOV
recruitingLocationsLOV Based on latest (2026.09)
Look up the list of values for Recruiting Locations LOV.
/hcmRestApi/resources/11.13.18.05/recruitingLocationsLOV
- Operations
- GET (list)GET (one)
- Record key
LocationFQN- Required on create
- no create on this resource
- At a glance
- 5 fields2 finders0 children
Try it
Response fields ·
Filters (q)
Only attributes Oracle marks as searchable are offered.
Finder
Paging and options
limit
GET /hcmRestApi/resources/11.13.18.05/recruitingLocationsLOV?fields=CityId,CountryId,GeographyId,LocationFQN,StateId&limit=25&onlyData=true
Response shape (placeholders)
{
"items": [
{
"CityId": "<string, max 255>",
"CountryId": "<string, max 255>",
"GeographyId": "<string, max 255>",
"LocationFQN": "<string, max 255>",
"StateId": "<string, max 255>"
}
],
"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 5
| Attribute | Type | Use |
|---|---|---|
CityId | text · max 255 | Read-onlySearchable |
CountryId | text · max 255 | Read-onlySearchable |
GeographyId | text · max 255 | Read-onlySearchable |
LocationFQN | text · max 255 | Searchable |
StateId | text · max 255 | 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 2
Predefined searches: ?finder=Name;variable=value,variable2=value2. Pick one in Try it to build the call.
findByGeographyId·GeographyIdfindByWord·DetailFlagFilterAttributesSearchTermsStartsWithFlag
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/recruitingLocationsLOVand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
findByGeographyIdfor 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:LocationFQN, notlocationfqn. - A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.