A point-in-time snapshot of everything a customer is currently entitled to.

Wire object entitlements.active_entitlement_summary. This object is delivered by webhook only — it arrives as the data.object of an entitlements.active_entitlement_summary.updated event, and Stripe serves it from no HTTP endpoint at all. There is therefore no retrieve/2 here, and that is not a gap: there is nothing to retrieve it from. The only way to obtain one is to receive it.

It also has no top-level id — the object carries no id property, not even an optional one, and no x-resourceId, which is an independent structural confirmation that it is not an addressable resource. The struct consequently has no :id field.

See Entitlements for the end-to-end story.

Stripe inlines at most ten entitlements

The nested entitlements envelope is a page, not a snapshot. Stripe inlines at most ten active entitlements and sets has_more when there are more. Treating that inline page as a complete picture is the bug this module was written to remove: a customer with eleven active entitlements looks unentitled to the eleventh, and a reconciler that writes the inline page to a local store revokes access the customer legitimately holds.

Use stream_entitlements!/3. It performs a full canonical re-fetch keyed on the summary's customer, at limit=100 per page, following has_more to the end. It ignores the inline page entirely and deliberately does not resume from its cursor — resuming would stitch a head-of-list captured when the webhook fired to a tail queried later, producing a hybrid whose ordering assumption spans two points in time. One call, one point in time.

The inlined url is rewritten

Stripe's webhook payload sets the inlined list's url to "/v1/customer/cus_ABC123customer/entitlements" — singular customer, path-scoped. That string is not one of the paths in Stripe's OpenAPI spec; its callability is not established and it 404s against stripe-mock. Because LatticeStripe.List.stream/2 builds each next page from list.url, this module rewrites the nested list's url to the canonical /v1/entitlements/active_entitlements, populates _params with the customer filter, and derives _last_id from the raw wire maps. A consumer who reaches for LatticeStripe.List.stream(summary.entitlements, client) instead of the blessed path therefore still gets a documented, callable, tenant-scoped request.

Reconciling from a webhook

alias LatticeStripe.Entitlements.ActiveEntitlementSummary

def reconcile_from_event(%LatticeStripe.Event{} = event, client) do
  summary = ActiveEntitlementSummary.from_map(event.data["object"])

  entitlements =
    client
    |> ActiveEntitlementSummary.stream_entitlements!(summary)
    |> Enum.to_list()

  MyApp.Entitlements.reconcile(summary.customer, entitlements)
end

Dispatch it from your LatticeStripe.Webhook.Handler on the entitlements.active_entitlement_summary.updated event type.

Gate your application against the local store that reconcile/2 writes — never against a network call on the authorization path. See LatticeStripe.Entitlements.ActiveEntitlement for why.