#Becca
1 messages · Page 1 of 1 (latest)
My use case here is that our subscription plan upgrades will be immediate but downgrades use a schedule to switch at the period end. If someone has a schedule active for a pending downgrade but upgrades or cancels in the meantime, I need to get the active schedule if it exists to release it, but if it's been released already I don't care about it. Passing a customer id and status filter means I would be expecting 0 or 1 items back, so it'd be nice not to have to handle list+paging and then filter by status in my own code (what would the sort order would be here?). [sorry, this turned into a few questions I guess...] thanks!
hello! sorry i can't think of any way either to only get schedules that have not been released or active. Perhaps the only way is to save the Subscription Schedule to your own DB and do your own filtering
I guess, just feels like a lot to do for something that should be simple. other "search" endpoints you can filter by status, but I guess this being "list" and not "search" doesn't have it? 😐
we don't have a search for Subscription Schedules yet from what I can see
you can search for Subscriptions, but not Subscription Schedules
these are two different types of objects
yeah, that's what I was trying to say, it's a list not search, hence less filtering
no way to use released_at to work around it?
you can test it to see if it works, i don't know off the top of my head if it would
the cli just yells about the parameter being unknown so that's made testing it a bit difficult hehe