#pickle-nick_api
sharp skiffBOT
👋 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/1387021687639511121
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
dapper bear
Hi 👋
Can you share a request ID that throws this error?
dapper bear
Can you share the request I that shows this error?
digital ocean
the api call?
dapper bear
It's in the request log url in the error message but I cannot copy the text from the screenshot
It starts with req_
digital ocean
There was an issue setting up your call.
Raw response for the API
Status code 400
{
"error": {
"code": "url_invalid",
"doc_url": "https://stripe.com/docs/error-codes/url-invalid",
"message": "Invalid URL: An explicit scheme (such as https) must be provided.",
"param": "success_url",
"request_log_url": "https://dashboard.stripe.com/test/logs/req_rK2vCwlASfe95y?t=1750762270",
"type": "invalid_request_error"
}
}
its happening across both orgaisations api calls
betterm2m and the aes global account
dapper bear
The cancel and success urls are the actual strings cancel_url: "_*_cancel_url_*_", and success_url: "_*_success_url_*_",
digital ocean
correct
dapper bear
AFAIK that has never been publicly supported
digital ocean
we are passing the same urls as before statrting with https://
we have worked this way for about 14 months now
dapper bear
You mean you did start with https:// before?
dapper bear
Well you are not passing https in these strings
digital ocean
we have about 600 partners using this platform without issues until today.
its not passing https? whaty is it passing?
dapper bear
I just shared the exact text with you
digital ocean
ahh, so its passing the dynamic parameter name instead of the value?
dapper bear
Correct
digital ocean
* are what we use to set the dyanmic labels, has there been an update that means thats no longer supported?
*
its not showing
_ * _ (without spaces
it wont show the underscore
underscore*underscore
dapper bear
We have always required that you pass valid strings that start with https://
dapper bear
It seems like the API connect you are using is not doing the substitution you expect
sharp skiffBOT
digital ocean
ahh, could this be a fault on bubbles side? (bubble api connector) not making those values dynamic?
like it always has until today>
?
dapper bear
Our SDKs do not perform any substitution
But since you are using a Connector there is every chance that is where the breakage occurred
digital ocean
right...so basically this is happening because my api connector client is ignoring the dynamic indicators?
and its passing the dynamic indicators instead of the dynamic values they refer to?
so on your side your not receiving any URL your just recieving the underscore*underscore dynamic value names?
dapper bear
All I can see is the actual parameter values that are passed. I have no insight into the connector's logic
We are receiving the exact values I provided
stray sonnet
hi! I'm taking over this thread.
digital ocean
The cancel and success urls are the actual strings `cancel_url: "_*_cancel_url_*...
you mean these values?
stray sonnet
you can see the exact information that Stripe received here: https://dashboard.stripe.com/test/logs/req_rK2vCwlASfe95y
there I see: cancel_url: "_*_cancel_url_*_" and success_url: "_*_success_url_*_".
stray sonnet
you are probably not logged in the correct account. but as mentioned above, this is what you sent to Stripe:
cancel_url: "_*_cancel_url_*_"andsuccess_url: "_*_success_url_*_"
