You are in the right place. You are a functional consultant. Agent Studio asks you for a REST endpoint and an OpenAPI spec, and the documentation is 400 pages. Ask here in plain words instead: you get the verified endpoint, the required parameters, the trap that causes the mystery 400, and a sample you can copy. No login, no reading marathon.
This preview holds 8 verified endpoints of the ~1,257 SCM and Procurement REST resources in our full library. Every card states how it was verified: live calls on a demo instance, or Oracle's 25D REST schemas with live describe snapshots. Sample IDs are placeholders, replace them with values from your instance, and verify there before production. Building the agent itself? Start with AI Agents Explained. Want the full library? 📮 Ask to be told when it ships.
Some resources require at least one filter before they answer. The classic is inventoryOnhandBalances: a plain GET returns HTTP 400 until you pass ItemNumber, OrganizationCode, InventoryItemId or OrganizationId in the q= parameter. The card above shows the working shape.
Far fewer than the metadata suggests. Oracle's describe lists many fields as "mandatory" that the system populates itself, sending them causes errors. Example: creating a draft purchase order needs only 3 of the 97 body properties. Each card above lists the true required set.
Yes, this is exactly what a Business Object definition in Agent Studio needs: the resource endpoint, which you then query for its OpenAPI spec, and the fields worth keeping. Knowing the required parameters and traps before you wire the tool saves the debugging afternoon.