Time Layout Sets
timeLayoutSets Based on latest (2026.09)
Look up Time Layout Sets, with web clock layouts. Read-only.
- Operations
- GET (list)GET (one)
- Record key
layoutSetId- Required on create
- no create on this resource
- At a glance
- 3 fields1 finders4 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /hcmRestApi/resources/11.13.18.05/timeLayoutSets?fields=geolocationEnabledFlag,layoutSetId,layoutSetName&limit=25&onlyData=true
{
"items": [
{
"geolocationEnabledFlag": false,
"layoutSetId": 0,
"layoutSetName": "<string, max 80>"
}
],
"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 3
| Attribute | Type | Use |
|---|---|---|
geolocationEnabledFlag | yes/no | Read-onlySearchable |
layoutSetId | number | Read-onlySearchable |
layoutSetName | text · max 80 | 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.
findByPersonIdAndEffectiveDate·effectiveDatepersonId
Check a payload
Checked in your browser only; nothing you paste is sent anywhere. Checks names and flags, not values.
Children 4
Child resources sit under one record: /hcmRestApi/resources/11.13.18.05/timeLayoutSets/{layoutSetId}/child/<name>. Add them to a GET with expand.
webClockLayoutsGET Web Clock Layouts · 12 fieldsallowChangeRequestForClockTimeFlagallowManualEntryFlagallowedTimeDifferencebuttonLogicEnabledFlagclockToUsedisplayTimeZoneFlaghideSecondsFlagrestartSequenceFlagshowDailyTimeEventsFlagtimeZoneEffectiveEndDatewebClockLayoutIdwebClockTimeZoneIdbuttonsGET Buttons · 4 fieldsbuttonIdbuttonLabeliconNamesequencetimeAttributesGET Time Attributes · 4 fieldsattributeIdattributeNameattributeValueattributeValueIdtimeCardFieldsGET Time Card Fields · 32 fieldsadministratorDataSourceIdallowChangeRequestFlagalternateNameIdattributeDataTypeattributeFieldIdbindTcfId1bindTcfId2bindTcfId3bindTcfId4bindTcfId5defaultValuedefaultValueDisplaydefaultValueUOMdisplayNamedisplaySequencedisplayTypeformatBasedFlagformatSubTypefunctionfunctionBasedOnAnothermaximumLengthmaximumValueminimumValuerequiredFlagrestURIscalespecificValuetimeAttributeNametimeCardFieldIdtimeCardFieldTypeunitOfMeasureuserDataSourceId
Use in AI Agent Studio
- Point a Business Object or REST tool at
/hcmRestApi/resources/11.13.18.05/timeLayoutSetsand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
findByPersonIdAndEffectiveDatefor 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:geolocationEnabledFlag, notgeolocationenabledflag. - A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.