#jimbottle_api

1 messages ¡ Page 1 of 1 (latest)

waxen pewterBOT
#

👋 Welcome to your new thread!

⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.

⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.

🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1329165133372457063

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

torpid meteor
#

Hello there

#

We really don't know much about Sigma here since we just focus on the API.

#

However, I'm not aware of Sigma carrying anything that would indicate a change to a Subscription over time.

#

You are best ingesting customer.subscription.updated Webhooks if you want that level of tracking.

timid nexus
#

thank you for the rapid response! Is there a team that might have details on how Sigma creates that subscription_item_change_events object? We ask because it appears that it has exactly what we need to capture the level of detail we need.
Filtering to type = customer.subscription.updated from the Events records gets us close but it returns quite a few more records then the ones displaying in subscription_item_change_events.

torpid meteor