Determining which feature to use

There is no simple algorithm for determining the appropriate feature to use. In some situations, it may be possible to use multiple features, but it's easier to write the code using one particular feature.

At a high level, composite requests are typically the most robust option. If there is a choice of which feature to use, it may be best or easiest to use composite requests.

The following guidelines may also help you determine the best feature to use:

• Use composite requests or request inclusion if:
  • All subrequests must succeed or fail as a unit.
  • Information must be passed from one subrequest to another.
  • The subrequests must use endpoints from different APIs.
• Use composite requests or batch requests if at least some of the subrequests are GETs, DELETEs, or business action POSTs.
• In PolicyCenter, you can use a composite request with the Graph API endpoints to create a complete account and submission and then quote and bind the submission.

There also may be some situations where a given technique is required. For example, in ClaimCenter, you can only create unverified policies through composite requests.