// fusionrest agent · hcm · list of values
Payroll Time Definitions List of Values
payrollTimeDefinitionsLOV Based on latest (2026.09)
Look up the list of values for Payroll Time Definitions.
/hcmRestApi/resources/11.13.18.05/payrollTimeDefinitionsLOV
- Operations
- GET (list)GET (one)
- Record key
TimeDefinitionId- Required on create
- no create on this resource
- At a glance
- 5 fields1 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/payrollTimeDefinitionsLOV?fields=DefinitionName,DefinitionType,LegislativeDataGroupId,Name,TimeDefinitionId&limit=25&onlyData=true
Response shape (placeholders)
{
"items": [
{
"DefinitionName": "<string, max 80>",
"DefinitionType": "<string, max 30>",
"LegislativeDataGroupId": 0,
"Name": "<string, max 240>",
"TimeDefinitionId": 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 5
| Attribute | Type | Use |
|---|---|---|
DefinitionName | text · max 80 | Read-onlySearchable |
DefinitionType | text · max 30 | Read-onlySearchable |
LegislativeDataGroupId | number | Read-onlySearchable |
Name | text · max 240 | Read-onlySearchable |
TimeDefinitionId | number | 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.
findByDefinitionTypeUsageType·DefinitionTypeLegislativeDataGroupIdUsageType
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/payrollTimeDefinitionsLOVand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
findByDefinitionTypeUsageTypefor 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:DefinitionName, notdefinitionname. - A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.