Contract Role Codes
contractContactRoleCodes Based on latest (2026.09)
Look up Contract Role Codes. Read-only.
The record key contractContactRoleCodesUniqID 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
contractContactRoleCodesUniqID- Required on create
- no create on this resource
- At a glance
- 8 fields1 finders0 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /fscmRestApi/resources/11.13.18.05/contractContactRoleCodes?fields=ContactRoleCode,ContactRoleSourceVo,ContactSourceCode,ContractTypeId,ExternalRoleFlag&limit=25&onlyData=true
{
"items": [
{
"ContactRoleCode": "<string, max 30>",
"ContactRoleSourceVo": "<string, max 1000>",
"ContactSourceCode": "<string, max 30>",
"ContractTypeId": 0,
"ExternalRoleFlag": false
}
],
"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 8
| Attribute | Type | Use |
|---|---|---|
ContactRoleCode | text · max 30 | Read-onlySearchable |
ContactRoleSourceVo | text · max 1000 | Read-onlySearchable |
ContactSourceCode | text · max 30 | Read-onlySearchable |
ContractTypeId | number | Read-onlySearchable |
ExternalRoleFlag | yes/no · max 1 | Read-onlySearchable |
Intent | text · max 30 | Read-onlySearchable |
Meaning | text · max 80 | Read-onlySearchable |
PartyRoleCode | text · max 30 | 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.
ContactRoleSourceFinder·ParamContactRoleCodeParamContactSourceCodeParamContractTypeIdParamPartyRoleCode
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
/fscmRestApi/resources/11.13.18.05/contractContactRoleCodesand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
ContactRoleSourceFinderfor 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:ContactRoleCode, notcontactrolecode. 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.