A summary list takes the same filters as its full list, and pages and orders its results the same way. Its summaries are the same objects that standard webhook payloads carry.
When to use a summary list
The full lists compute what they return for each object on the page: a subscription’s price intervals and billing periods, or an invoice’s line items. That work grows with each subscription’s history and each invoice’s size, so pages of large subscriptions or invoices can take seconds to return. A summary list reads only each object’s own fields, so its pages stay quick however large the objects are. Use a summary list when you only need to know which subscriptions or invoices exist and their state, for example to sync them into another system, to check statuses, or to find the objects that need more work. Use the full list when you need what the summary leaves out for most of the page. When you need the full object for only some of the results, page through the summary list and fetch those objects with Fetch subscription or Fetch invoice:Using the summary lists from the SDKs
Each method returns a page you can iterate through, like the SDK’s other list methods.