Job Application Grid View Categories
recruitingGridViewCategoriesLOV Based on latest (2026.09)
Look up the list of values for Job Application Grid View Categories.
The record key recruitingGridViewCategoriesLOVUniqID 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
recruitingGridViewCategoriesLOVUniqID- Required on create
- no create on this resource
- At a glance
- 10 fields1 finders0 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /hcmRestApi/resources/11.13.18.05/recruitingGridViewCategoriesLOV?fields=CategoryCode,CategoryDescription,CategoryDisplayName,CategoryName,CategoryType&limit=25&onlyData=true
{
"items": [
{
"CategoryCode": "<string>",
"CategoryDescription": "<string>",
"CategoryDisplayName": "<string>",
"CategoryName": "<string>",
"CategoryType": "<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 10
| Attribute | Type | Use |
|---|---|---|
CategoryCode | text | Searchable |
CategoryDescription | text | Searchable |
CategoryDisplayName | text | Searchable |
CategoryName | text | Searchable |
CategoryType | text · max 255 | Searchable |
ContextCode | text · max 255 | Searchable |
MultiRowFlag | yes/no | Searchable |
ProfileContentTypeId | number | Searchable |
ProfileSectionId | number | Searchable |
ProfileSectionName | 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 1
Predefined searches: ?finder=Name;variable=value,variable2=value2. Pick one in Try it to build the call.
findByWord·ContextCodeDisplayProfileSectionsFilterAttributesSearchTermsStartsWithFlag
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/recruitingGridViewCategoriesLOVand 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:CategoryCode, notcategorycode. onlyData=trueremoveslinks, and this resource's key only comes fromlinks. Leave it off when you need the key.- A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.