Web Clock Events
webClockEvents Based on latest (2026.09)
Create and look up Web Clock Events, with time card fields.
- Operations
- GET (list)GET (one)POST (create)
- Record key
webClockClickId- Required on create
buttonIdeventSourcepersonId- At a glance
- 16 fields1 finders1 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /hcmRestApi/resources/11.13.18.05/webClockEvents?fields=ChangeRequestPendingFlag,DeviceType,EventType,GeoLocation,GeoLocationException&limit=25&onlyData=true
{
"items": [
{
"ChangeRequestPendingFlag": false,
"DeviceType": "<string, max 30>",
"EventType": "<string, max 255>",
"GeoLocation": "<string, max 150>",
"GeoLocationException": "<string, max 30>"
}
],
"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 16
| Attribute | Type | Use |
|---|---|---|
ChangeRequestPendingFlag | yes/no · max 1 | Read-onlySearchable |
DeviceType | text · max 30 | Optional on createSearchable |
EventType | text · max 255 | Read-onlySearchable |
GeoLocation | text · max 150 | Optional on createSearchable |
GeoLocationException | text · max 30 | Optional on createSearchable |
Status | text · max 255 | Read-onlySearchable |
TimeEventId | number | Optional on createSearchable |
buttonId | number | Required on createSearchable |
buttonLabel | text · max 150 | Read-onlySearchable |
deviceClickTime | text · max 80 | Optional on createSearchable |
eventSource | text · max 40 | Required on createSearchable |
iconName | text · max 150 | Read-onlySearchable |
personId | number | Required on createSearchable |
serverClickTime | text | Optional on createSearchable |
timeTamperedFlag | yes/no | Optional on createSearchable |
webClockClickId | number | Optional on createSearchable |
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.
findByStartDateStopDate·startDatestopDate
Check a payload
Checked in your browser only; nothing you paste is sent anywhere. Checks names and flags, not values.
Children 1
Child resources sit under one record: /hcmRestApi/resources/11.13.18.05/webClockEvents/{webClockClickId}/child/<name>. Add them to a GET with expand.
timeCardFieldsGET · POST Time Card Fields · 5 fieldstimeCardFieldDisplayNametimeCardFieldIdtimeCardFieldNametimeCardFieldValuetimeCardFieldValueId
Use in AI Agent Studio
- Point a Business Object or REST tool at
/hcmRestApi/resources/11.13.18.05/webClockEventsand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
findByStartDateStopDatefor 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.
- This resource can change data. Put a human approval step before any create, update, delete or action call.
More in For Builders.
Pitfalls
- Attribute names are case-sensitive in
q,fieldsand bodies:DeviceType, notdevicetype. - 5 fields are read-only: sending them in POST or PATCH fails or is ignored. The builder leaves them out.
- A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through. - Text fields have maximum lengths (shown in the field table). Longer values are rejected.