#ostermi_webhooks
agile wadiBOT
đ 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/1402281003665592442
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
lucid hearth
I have tried to set my Stripe-Version but i got the following message : "message": "Invalid Stripe API version: 2028-08-01",
That is an invalid date in the future with no such API version
Did you mean to use 2022-08-01 there, as in the example request you shared?
You can use the Webhook Endpoints api to create endpoints with any valid version you want, the account default version is only use when not specified.
With the dashboard you're more limited, but not via the API
ocean phoenix
The issue is that i tried to create a webhook with api-version 2022-08-01 but it is not taken in account the param connect=true
curl https://api.stripe.com/v1/webhook_endpoints -u "sk_test...:" -H "Stripe-Version: 2022-08-01" -d "enabled_events[]"="account.updated" -d "connect"="true" -d "api_version"="2022-08-01" --data-urlencode url="https://test.test"
this is working on all the environment i created but not in the one i created today
and i can't change all my backend call to add -H "Stripe-Version: 2022-08-01"
ocean phoenix
Did you mean to use 2022-08-01 there, as in the example request you shared?
yes is what i meant, sorry for the typo
lucid hearth
backend call to add -H "Stripe-Version: 2022-08-01"
This shouldn't be necessary, thats the API version of the request you making, which is separate from theapi_versionyou want to set for the endpoint
Can you share that request ID you made to create this endpoint?
ocean phoenix
> backend call to add -H "Stripe-Version: 2022-08-01"
This shouldn't be necessar...
but as my new account is in newer version my old requests were made for 2022-08-01 they won't work on the new account or am i missing something ?
lucid hearth
Leaving out version pinning in SDKs, APi requests can be made with ~any API version in the header overrides, regardless of the account default version (there are some edge cases for certain types of requests with some deprecated features/params etc)
And your account using a newer version (by default, or override) will still generate events in the specified older version for an endpoint, thats not an issue
Does that address your concern? If not, I need you yo clarify what you're worried about
lucid hearth
req_OGjhqG977fUZiy
This request looks fine to me, and sets up an endpoint using the 2022-08-01 api version for the event payload shape
agile wadiBOT
ocean phoenix
yes it is working with all other accounts, but not with the new ones, it ignores the connect=true :/
lucid hearth
oh, interesting. I do see that. Hmm
thorn sand
Looking in to this. Have you been able to successfully create Connect webhook endpoints before? Or is this the first time you are trying via the API and it has always done this?
Also just to make sure, you are saying that without the version we do respect the Connect setting?
ocean phoenix
no i have about 5 other account and it is working
ocean phoenix
Also just to make sure, you are saying that without the version we do respect th...
with an account with the api_version 2022-08-01, I don't have an issue to create webhook with connect=true. but now with this newly created account with version 2025-07-30.basil it seems i can't create "connected webhook" anymore
thorn sand
Ah it looks like this may be happening because the account you are currently testing on isn't a platform account. I will file feedback because we should error rather than dropping the param unintentionally but the params should work on test accounts that are platforms
ocean phoenix
I can try to finish the "account" in order to be a platform account
the request id : req_UtmvP57u4Xzre0
I tested on the "platform account" but not in livemode
thorn sand
Interesting, that account also doesn't look to be a platform as far as I can see
Can you send me the endpoint ID from an account where these parameters do both work together?
ocean phoenix
yes
the request from yesterday on an old account : req_tPqWyGoge0PV2u and the webhook created : we_1RsQSJKstSA23JNk5tTFmusX
thorn sand
Gotcha, that does seem to fit the pattern of this working for platform accounts but not for accounts that haven't been set up that way yet. I wonder if this is because it relies on a connect application existing (the ca_ field returned on the connect endpoint) on the account that is making the call. Will see if I can test this on one of my test accounts quickly
But my current best guess is that you will need to complete Connect setup on the account(s) that this currently isn't working on that you want to set these endpoints up for
ocean phoenix
ok will try also to create a first connected account and test again
req_1K8EsEGsJwUcfN & we_1RsmvMDIU39JQNgyRBb1myai ! it seems that was because the connected account configuration was not yet finished !
also, normally all my old api calls should work ? the ones to create redirect url, to transfer money to connected account even if my account is in newer version ?
thorn sand
Yep, the actions on the account are the same, the main thing API versions do is define what actions are possible with the specific call you are making and how the API object is rendered when it is returned to you
ocean phoenix
thanks a lot for your reactivity and your help !
thorn sand
If course, happy we could help you resolve this!