Teams Incoming Webhook response Bad payload received by generic incoming webhook

Question

Teams Incoming Webhook response Bad payload received by generic incoming webhook

양정우 [pororoca] 20

Hello,

Recently, I found about Teams Incoming Webhook response is error, and the content is as in the title, wrote above.

We have been sending request via .net httpclient, to Teams Incoming Webhook connector.

And we did set request header as below.

ContentType = application/x-www-form-urlencoded

I did read documentation about Teams Incoming Webhook at recent, and I found out Content-Type have to set 'application/json'. Also I checked this by toy-project.

But I was confused, because our program used that content-type last years, and it did work.

I tried to figure out this, and I found this question.

[Solved] Teams Incoming Webhook: Bad payload received by generic incoming webhook

This case is very similar with our case.

I was wondering about, is there anything changed about Teams Incoming Webhook?
And if so, where I can found that?

Thanks.

Ran Hou-MSFT 7,585 Reputation points Microsoft External Staff

2023-07-24T08:49:14.4533333+00:00

@양정우 [pororoca]

I am checking the status of this case. Please let us know if you would like further assistance.

Meanwhile, if the reply is helpful to you, please try to mark it as an answer, it will help others who encounter the same issue and read this thread.

Thank you for your understanding and patience!

Accepted answer

2 additional answers

Your answer

Ran Hou-MSFT 7,585 Reputation points Microsoft External Staff

2023-07-24T08:49:14.4533333+00:00

@양정우 [pororoca]

I am checking the status of this case. Please let us know if you would like further assistance.

Meanwhile, if the reply is helpful to you, please try to mark it as an answer, it will help others who encounter the same issue and read this thread.

Thank you for your understanding and patience!

Answer 1

Prasad-MSFT 9,061 Microsoft External Staff Moderator

양정우 [pororoca] - We got confirmation from engineering team that, "As per our docs, webhook messages should be of type JSON in HTTP POST headers: Create and send messages - Teams | Microsoft Learn".

The old backend was allowing other content types as well, but in the new backend we have support for JSON only in line with our public documentation.

Thanks,

Prasad Das

*************************************************************************

If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link. Click here to escalate.

양정우 [pororoca] 20 Reputation points

2023-08-02T07:54:35.51+00:00

Thank you and Sorry for late check.

Now it make sense about why our teams webhook request worked well before.

Our request's content body encoded to JSON, but 'content-type' header was set by 'urlencoded'. (We fixed this already)

As a result, our 'request form' was originally incorrect.

But it seems to be, at old-backend accepted without consider about 'content-type' header.

And now, based on your answer, I guess new backend start checking header type.

Thank you again!

Answer 2

Prasad-MSFT 9,061 Microsoft External Staff Moderator

양정우 [pororoca]
We tried using below JSON

{
    "@type": "MessageCard",
    "@context": "http:\/\/schema.org\/extensions",
    "themeColor": "d58200",
    "title": "title",
    "text": "text",
    "potentialAction": [
        {
            "@type": "OpenUri",
            "name": "Name",
            "targets": [
                {
                    "os": "default",
                    "uri": "https:\/\/www.example.com\/"
                }
            ]
        }
    ]
}

User's image

and observed that the card is getting posted successfully in Teams channel.
User's image

Did you try adding the following header to the request and check if it works?

Content-Type: application/json

Thanks,

Prasad Das

*************************************************************************

If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link.

양정우 [pororoca] 20 Reputation points

2023-07-13T07:25:34.3233333+00:00

sorry about duplicate comment

please check below comments.
양정우 [pororoca] 20 Reputation points

2023-07-13T07:26:55.2666667+00:00

Thank you for your answer.

And sorry, I guess I didn't convey to you about my intentions accurately.

(I already tried to change content-type to 'application/json', and I checked that works well again.)

I have one more question, as I wrote at my question above.

I was wondering about, is there anything changed about Teams Incoming Webhook? And if so, where I can found that?

Because, our content-type of request was set by 'application/x-www-form-urlencoded' since 2020

And it did work at least until 7 days ago as I checked by channel.

So I just wanted to know is there anything change in Teams Incoming Webhook process.

P.S

P.S

We did upgrade our project's .net version on January this year, and changed deprecated functions something likes WebRequest process to HttpClient.

But that change was already passed about several months.

And Teams Incoming Webhook response issue occur since 2023/07/06, so I couldn't think about our .net upgraded was related this issue.

If there wasn't any changed, then I have to check another side.
Prasad-MSFT 9,061 Reputation points Microsoft External Staff Moderator

2023-07-13T14:09:35.0566667+00:00

Okay got it. Let me check this with engineering team if there are any changes made from Teams Incoming Webhook.
I will update this thread as soon as i hear back. Thanks!
Prasad-MSFT 9,061 Reputation points Microsoft External Staff Moderator

2023-07-13T14:09:46.0233333+00:00

Okay got it. Let me check this with engineering team if there are any changes made from Teams Incoming Webhook.
I will update this thread as soon as i hear back. Thanks!
Ran Hou-MSFT 7,585 Reputation points Microsoft External Staff

2023-07-20T01:28:30.5733333+00:00

양정우 [pororoca]

Just checking in to see if above information was helpful. If you have any further updates on this issue, please feel free to post back. If you think my reply is helpful to you, please remember to mark it as an answer. Warm thanks.

Answer 3

양정우 [pororoca]
We tried with below JSON

{
    "@type": "MessageCard",
    "@context": "http:\/\/schema.org\/extensions",
    "themeColor": "d58200",
    "title": "title",
    "text": "text",
    "potentialAction": [
        {
            "@type": "OpenUri",
            "name": "Name",
            "targets": [
                {
                    "os": "default",
                    "uri": "https:\/\/www.example.com\/"
                }
            ]
        }
    ]
}

and observed that the card is getting posted successfully in Teams channel.
User's image

Did you try adding the following header to the request and check if it works?
Content-Type: application/json

Thanks,

Prasad Das

*************************************************************************

If the response is helpful, please click "Accept Answer" and upvote it. You can share your feedback via Microsoft Teams Developer Feedback link.

Share via

Teams Incoming Webhook response Bad payload received by generic incoming webhook

2 additional answers

Your answer