#karma-foundation_webhooks

1 messages ยท Page 1 of 1 (latest)

vague vesselBOT
#

๐Ÿ‘‹ 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/1295576055955853343

๐Ÿ“ Have more to share? Add more details, code, screenshots, videos, etc. below.

grizzled cedarBOT
cerulean cloud
#

Hi

lethal marsh
cerulean cloud
#

I have receved the webhook on my server

#

evt_1Q9N3AKXSEvkiZUFUXrnSZIo

#

This is the event ID for today morning

lethal marsh
#

Stripe sent the request as Content-Type: application/json, but looks like some middleware in your service converted into Content-Type: application/xml that results in failing to parse the object. I'd recommend checking how to parse the event with stripe-dotnet library: https://docs.stripe.com/webhooks?lang=dotnet#example-endpoint

Listen to events in your Stripe account on your webhook endpoint so your integration can automatically trigger reactions.

cerulean cloud
#

Hi. I have tried this, but in vain

#

If you could help fix this it will be great

lethal marsh
#

I'm not familiar with c#. As a first step, I'd recommend checking why the request was turned into xml instead of json. Likely somewhere in your server configuration (other parts of your code) set to parse the request into xml

cerulean cloud
#

OK

#

This same code was working earlier

#

So I dont know what the issue could be

lethal marsh
#

We don't have the visibility how your server parse the request and whether there is any change has been made at your server. From the event request sent from Stripe, the format has always been Content-Type: application/json.

#

From the error message you shared, the request has transformed into Content-Type: application/xml somewhere in your system that causes failure to serialise the object