// fusionrest agent · hcm
Recruiting Event Check In Processes
recruitingCEEventRegistrationCheckIns Based on latest (2026.09)
Create Recruiting Event Check In Processes.
/hcmRestApi/resources/11.13.18.05/recruitingCEEventRegistrationCheckIns
- Operations
- POST (create)
- Record key
EventNumber- Required on create
- none marked
- At a glance
- 4 fields0 finders0 children
I want to…Create one
Try it
Request body (required ones are included)
POST /hcmRestApi/resources/11.13.18.05/recruitingCEEventRegistrationCheckIns Content-Type: application/vnd.oracle.adf.resourceitem+json
Request body (placeholders)
{}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 4
| Attribute | Type | Use |
|---|---|---|
EmailId | text | Optional on create |
PhoneNumber | text · max 255 | Optional on create |
Action | text · max 255 | Optional on create |
EventNumber | text | Optional on create |
Names, types, labels and flags from Oracle's REST specification (latest (2026.09)). Flexfield and custom attributes vary by pod: check /describe for yours.
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/recruitingCEEventRegistrationCheckInsand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - 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:EmailId, notemailid. - Text fields have maximum lengths (shown in the field table). Longer values are rejected.