Recruiting CE Candidate Site Preferences
recruitingCECandidateSitePreferences Based on latest (2026.09)
Create and look up Recruiting CE Candidate Site Preferences, with site TC preferences.
- Operations
- GET (list)GET (one)POST (create)
- Record key
CandidateNumber- Required on create
- none marked
- At a glance
- 7 fields0 finders4 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /hcmRestApi/resources/11.13.18.05/recruitingCECandidateSitePreferences?fields=Action,CampaignCode,CandidateCountry,CandidateNumber,Context&limit=25&onlyData=true
{
"items": [
{
"Action": "<string>",
"CampaignCode": "<string>",
"CandidateCountry": "<string>",
"CandidateNumber": "<string, max 255>",
"Context": "<string>"
}
],
"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 7
| Attribute | Type | Use |
|---|---|---|
Action | text | Optional on createSearchable |
CampaignCode | text | Optional on createSearchable |
CandidateCountry | text | Optional on createSearchable |
CandidateNumber | text · max 255 | Optional on createSearchable |
Context | text | Optional on createSearchable |
OptInMarketingEmailFlag | yes/no · max 30 | Optional on create |
SiteNumber | text | 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.
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/recruitingCECandidateSitePreferences/{CandidateNumber}/child/<name>. Add them to a GET with expand.
siteTCPreferencesGET · POST Preferred Site TC in the Site Preferences of the Recruiting Candidate · 4 fieldsFlowVersionIdLegalDescriptionVersionIdOptInJobAlertFlagSiteNumberpreferredJobFamiliesGET · POST Preferred Job Families · 1 fieldsJobFamilyIdpreferredJobFunctionsGET · POST Preferred Job Functions · 1 fieldsJobFunctionCodepreferredLocationsGET · POST Preferred Locations · 1 fieldsGeographyId
Use in AI Agent Studio
- Point a Business Object or REST tool at
/hcmRestApi/resources/11.13.18.05/recruitingCECandidateSitePreferencesand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - 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:Action, notaction. - 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.