Employee Communication Sender Profiles List of Values
employeeCommunicationSenderProfilesLOV Based on latest (2026.09)
Look up the list of values for Employee Communication Sender Profiles.
The record key employeeCommunicationSenderProfilesLOVUniqID is a generated hash. Take it from the record's links (rel self) in a GET response; never build it yourself.
- Operations
- GET (list)GET (one)
- Record key
employeeCommunicationSenderProfilesLOVUniqID- Required on create
- no create on this resource
- At a glance
- 7 fields1 finders0 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /hcmRestApi/resources/11.13.18.05/employeeCommunicationSenderProfilesLOV?fields=ConfigId,ConfigName,ReplyToDisplayName,ReplyToEmail,SenderDisplayName&limit=25&onlyData=true
{
"items": [
{
"ConfigId": 0,
"ConfigName": "<string, max 240>",
"ReplyToDisplayName": "<string, max 240>",
"ReplyToEmail": "<string, max 240>",
"SenderDisplayName": "<string, max 240>"
}
],
"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 |
|---|---|---|
ConfigId | number | Read-onlySearchable |
ConfigName | text · max 240 | Read-onlySearchable |
ReplyToDisplayName | text · max 240 | Read-onlySearchable |
ReplyToEmail | text · max 240 | Read-onlySearchable |
SenderDisplayName | text · max 240 | Read-onlySearchable |
SenderEmail | text · max 240 | Read-onlySearchable |
TeamId | number | 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.
findById·TeamId
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/employeeCommunicationSenderProfilesLOVand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
findByIdfor 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:ConfigId, notconfigid. onlyData=trueremoveslinks, and this resource's key only comes fromlinks. Leave it off when you need the key.- A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.