#corollamango74

1 messages · Page 1 of 1 (latest)

static streamBOT
solemn horizon
#

👋 No, we don't reopen threads but happy to continue helping!

strong void
#

Thank you! I added the cancel_at_period_end to the body and received the same error. This is the Id for the failed API error: req_nLVA1EHHqJtRod

solemn horizon
#

Thanks! The request looks similar to the one you shared with my teammate earlier. The subscription ID in the request looks wrong/isn't being dynamically changed

#

The subscription ID we received as part of req_nLVA1EHHqJtRod isn't in the shape I'd expect it to be. It should look like sub__... (with a single underscore after sub)

strong void
#

So it seems like in my chatbot software, the API call I'm making isn't dynamically updating the subscription ID as it should and that’s what is causing the error?

Is it possibele to share an image of my API request because I did have the cancel_at_period_end=true in the URL and it was working.

Does it need to be in the body, or is there a way to tell which parameters need to be in the body and which should be in the url?

#

I don't know if this is helpful but this is what I am working with in the chatbot flows.

Screen_Shot_2023-05-16_at_3.55.12_PM.png
solemn horizon
#

The issue here is the request we're receiving is a POST request to v1/subscriptions/%7B%7Bf41380v263548%7D%7D (this is {{f41380v263548}} but URL encoded)

strong void
#

That's really interesting. Is this also the case for checkout links, invoice objects, and everything else regarding parameters?

solemn horizon
#

For the most part, though our search endpoints expect the search parameters in the URL

strong void
#

That's very helpful to know. Thank you very much! I'll reach out to the chatbot company since it seems to be on their side. Thank you!

solemn horizon
#

Yep, something is definitely amiss. In the screenshot above, you can see the expected subscription ID above the URL Params, Headers, etc. row but that's somehow not being received on our end