Using Siebel REST API to Access Siebel Business Objects JSON Examples
You can use the Siebel REST API to access Siebel CRM Business Objects. Users can perform QUERY, INSERT, UPDATE, and DELETE operations on the Siebel Business Objects using REST API requests over HTTP as described in this section.
This topic includes the following information:
Querying for a Siebel CRM Business Component with a Search Specification
Querying for a Siebel CRM Business Component Record to Return a Subset of Fields
-
Querying a Root Business Component Using the recordcountneeded Parameter
-
Querying A Root Business Component Using the recordneeded and Viewmode Parameters
-
Querying Child Business Components Using the recordcountneeded Parameter
-
Querying Grandchildren Business Components Using the recordcountneeded Parameter
-
Querying for a Siebel CRM Business Component with a Sort Specification
Inserting Multiple Siebel CRM Business Components When a Record Already Exists
Deleting Multiple Siebel CRM Business Components When A Record is Already Deleted
Delete Multiple Siebel CRM Business Components with Identifier in the URL and in the Request Body
Querying for a Siebel CRM Business Component To Return a Subset of Child Links
-
Querying for a Siebel CRM Child Business Component To Return Its Child Links
Querying for a Siebel CRM Business Component by Specifying the ViewMode Parameter
Querying for a Siebel CRM Business Component To Return No Child Links
Using the Describe Parameter to Return a REST Resource’s Metadata
Using the Describe Parameter to Return the Siebel Base Business Object Catalog
Using the Describe Parameter to Return Business Component Metadata
Using the Describe Parameter to Return Child Business Component Metadata
Using the Describe Parameter to Return OpenAPI Description of Multiple Object Operations
Querying for All Contacts in an Account Without Using Uniformresponse to Return a Single Record
Querying for All Contacts in an Account Using Uniformresponse to Return Multiple Records
Querying for All Contacts in an Account Without Using Uniformresponse to Return Multiple Records
Querying for a Single Account Record Without Using Uniformresponse
Using the Developer Workspace Parameter to Preview Changes Without Compiling to the Repository