Product Structure Hierarchies
structureHierarchies Based on latest (2026.09)
Look up Product Structure Hierarchies. Read-only, list only.
Oracle's specification marks GET (one) as not supported on this resource.
- Operations
- GET (list)GET (one)
- Record key
Id- Required on create
- no create on this resource
- At a glance
- 10 fields1 finders0 children
Try it
Only attributes Oracle marks as searchable are offered.
GET /crmRestApi/resources/11.13.18.05/structureHierarchies?fields=HierarchyLevel,Id,ItemDescription,ItemId,ItemName&limit=25&onlyData=true
{
"items": [
{
"HierarchyLevel": 0,
"Id": 0,
"ItemDescription": "<string, max 4000>",
"ItemId": 0,
"ItemName": "<string, max 255>"
}
],
"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 10
| Attribute | Type | Use |
|---|---|---|
HierarchyLevel | number | Read-onlySearchable |
Id | number | Read-onlySearchable |
ItemDescription | text · max 4000 | Read-onlySearchable |
ItemId | number | Read-onlySearchable |
ItemName | text · max 255 | Read-onlySearchable |
ItemNumber | text · max 300 | Read-onlySearchable |
ItemSequenceNumber | number | Read-onlySearchable |
OrgId | number | Read-onlySearchable |
ParentId | number | Read-onlySearchable |
ParentItemId | 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.
getStructureHierarchy·Bind_HierarchyLevelBind_IdBind_OrgId
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
/crmRestApi/resources/11.13.18.05/structureHierarchiesand ask only for the fields the agent needs withfields=. Big responses cost tokens and slow the agent. - Prefer a finder such as
getStructureHierarchyfor 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:HierarchyLevel, nothierarchylevel. - A list returns 25 rows unless you set
limit; readhasMoreand moveoffsetto page through.