tungtn1099

[serene briar]

Well you could check the previous_attributes hash on the payload. If it's a downgrade/upgrade then there'll likely be an items field in that hash

[slow marten]

Weird, my event data object is missing that hash

[serene briar]

Can you share an example?

[slow marten]

Oh wait, should it be outside of the event.data.object?

[serene briar]

Yes: event.data.previous_attributes (https://stripe.com/docs/api/events/object#event_object-data-previous_attributes)

[slow marten]

Alright I see, thanks!

previous_attributes: {
      billing_cycle_anchor: 1697861376,
      current_period_end: 1713672576,
      current_period_start: 1697861376,
      items: [Object],
      latest_invoice: <redacted>,
      plan: [Object]
    }

It says

[serene briar]

Well that's just a TS compiler error because there's no fields in the interface: https://github.com/stripe/stripe-node/blob/5bfdacac2119cf262e3dede30173b41167456276/types/Events.d.ts#L101

Probably safe to just ts-ignore that

[slow marten]

got it, thanks

[serene briar]

Or feel free to type it yourself based on the fields you need to check

[slow marten]

I think it creates a build error on deployment since we ignore node_modules no?

[serene briar]

I don't understand. You'd just create your own interface and then cast previous_attributes:

interface SubPrevAttr {
  items: Stripe.ApiList<SubscriptionItem>
}

event.data.previous_attributes as SubPrevAttr

Sorry can't remember the exact interface names