#mulo_code
wintry basinBOT
đ 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/1364259112312901716
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
tribal pier
Hello, yes that sub_123 ID is the Stripe ID for the subscription
https://docs.stripe.com/api/subscriptions/object#subscription_object-id
So that is the ID we will send in customer.subscription.* events for that subscription
tribal pier
Yep, that should set the subscription to cancel at the period end if you pass a valid ID
sterile flint
const subscription = await stripe.subscriptions.update(
agreementId,
{cancel_at_period_end: false }
);
if (subscription..
what should I look for when the request is acknowledged and everything is correct?
*and what for errors
tribal pier
We have this doc on errors https://docs.stripe.com/api/errors
sterile flint
The newly updated Subscription object, if the call succeeded. If payment_behavior is error_if_incomplete and a charge is required for the update and it fails, this call raises an error, and the subscription update does not go into effect.```
if *anything* goes wrong what kind of error do I get, string?I reccommend making the call in test mode to see what the successful response looks like. Youget a full subscription object back
You get a full error object, that doc lays out what they look like
sterile flint
ah wait, so should be in a try catch and in the latter i'd get the error? or i get the error as a good response?
tribal pier
Apologies I thought I linked to a different doc. This doc shows how to handle errors across our various client libraries, for Node it does look like we throw exceptions for that kind of error
https://docs.stripe.com/error-handling
sterile flint
const stripe = new Stripe(prodSecret, {apiVersion: '2022-11-15',});
try {
const subscription = await stripe.subscriptions.update(
agreementId,
);
return res.status(200)
} catch (err) {
if (err instanceof Stripe.errors.StripeError) {
switch (err.type) {
case 'StripeCardError':
console.error('Card error:', err.message);
return res.status(402).json({ error: err.message });
case 'StripeRateLimitError':
console.error('Rate limit error:', err.message);
return res.status(429).json({ error: 'Too many requests. Please try again later.' });
case 'StripeInvalidRequestError':
// Invalid parameters were supplied to Stripe's API
console.error('Invalid request:', err.message);
return res.status(400).json({ error: err.message });
case 'StripeAPIError':
console.error('Stripe API error:', err.message);
return res.status(500).json({ error: 'An internal error occurred. Please try again.' });
case 'StripeConnectionError':
// Some kind of error occurred during the HTTPS communication
console.error('Connection error:', err.message);
return res.status(502).json({ error: 'Network communication failed. Please try again.' });
case 'StripeAuthenticationError':
// You probably used an incorrect API key
console.error('Authentication error:', err.message);
return res.status(401).json({ error: 'Authentication with Stripe failed.' });
default:
console.error('Unexpected Stripe error:', err.message);
return res.status(500).json({ error: 'An unexpected error occurred.' });
}
} else {
console.error('Unexpected error:', err);
return res.status(500).json({ error: 'An unexpected error occurred.' });
}
}
This update wouldn't do anything because you are just passing the ID, otherwise the structure of that code looks fine. I'd reccommend running your code to test it out. That will evaluate it much better than we can on this server just by looking at it.
agreementId,
);```right, but if I do
const subscription = await stripe.subscriptions.update(
agreementId,
{ cancel_at_period_end: false }
);
it's implied it's a cancellation?
i think I should rather do
await stripe.subscriptions.del(subscriptionId);
marsh parrot
With cancel_at_period_end set to false, the subscription will not be canceled. Only when this parameter is set to true, the subscription will be canceled at the end of current cycle.
If you'd like to cancel the subscription immediately, stripe.subscriptions.cancel(...) should be used instead. See the guides here for more information:
- Cancel subscription API: https://docs.stripe.com/api/subscriptions/cancel?lang=node
Here's the doc about canceling a subscription: https://docs.stripe.com/billing/subscriptions/cancel?dashboard-or-api=api
sterile flint
thanks
then same cach logic applies
marsh parrot
Yes! The catch try-catch block applies to functions to Stripe API