// fusionrest agent · hcm
Internal Candidate Assessments
recruitingUICandidateAssessments Based on latest (2026.09)
Create and look up Internal Candidate Assessments.
/hcmRestApi/resources/11.13.18.05/recruitingUICandidateAssessments
- Operations
- GET (list)GET (one)POST (create)
- Record key
RequisitionId- Required on create
- none marked
- 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/recruitingUICandidateAssessments?fields=AssessmentCompletedFlag,AssessmentConfiguredFlag,AssessmentURL,DraftId,RequisitionId&limit=25&onlyData=true
Response shape (placeholders)
{
"items": [
{
"AssessmentCompletedFlag": false,
"AssessmentConfiguredFlag": false,
"AssessmentURL": "<string>",
"DraftId": 0,
"RequisitionId": 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 |
|---|---|---|
AssessmentCompletedFlag | yes/no | Read-onlySearchable |
AssessmentConfiguredFlag | yes/no | Read-onlySearchable |
AssessmentURL | text | Optional on createSearchable |
DraftId | number | Optional on createSearchable |
RequisitionId | 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.
findByRequisitionId·DraftIdRequisitionId
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/recruitingUICandidateAssessmentsand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
findByRequisitionIdfor 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:AssessmentURL, notassessmenturl. - 2 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.