Accessing deleted resources

[Adam Pearse]

Hi there,

Are deleted plans and coupons only accessible as nested resources on invoice objects? If so, would you consider adding a query parameter to the plan and coupon list endpoints to indicate that deleted resources should also be included?

My use case is that paginating through lists of unique resources in a known (reverse chronological) sort order simplifies the process of bulk exporting Stripe account data. It's much easier to reason about failure modes and recovery steps in that scenario than when identifying, deduping, and inserting deleted plans and coupons as a side effect of importing invoice data. 

Relatedly, a reply on a previous thread mentioned an explicit export API was under consideration. That would be fantastic! :)

Thanks,

Adam

[Jim Danz]

Hi Adam,

Unfortunately, the way it stands right now, allowing deleted coupons
and plans to show up in lists wouldn't be fully coherent because we
allow users to recycle IDs of plans and coupons that they've deleted.

I'd classify this as a "design mistake" on our part in that it
provides some unfortunate limits around your ability to reason about
historical Stripe data (you could have any number of plan "foo"s that
you can't differentiate between other than via their properties).

I'm going to be flagging this issue internally to see what we can do
to have a better story here, but with apologies I don't have a great
answer for you now.

Jim

> --
> You received this message because you are subscribed to the Google Groups
> "Stripe API Discussion" group.
> To post to this group, send email to api-d...@lists.stripe.com.
> Visit this group at
> http://groups.google.com/a/lists.stripe.com/group/api-discuss/.
>
> To unsubscribe from this group and stop receiving emails from it, send an
> email to api-discuss...@lists.stripe.com.