MS Teams "Send Channel Message" & 404 Not Found
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
13-12-21 05:25 AM
Dear Support
While we are testing the MS Teams VBO, came across the 404 Not Found response to the Send Channel Message. Based on the response, we would like to look into the RequestURI of the "Send Channel Message" but can't find where.
Q1. What are possible reasons for 404 Not Found?
Q2. Is there any way to look into the HTTP Request message? or
Q3. Could the "webURL" included in the 404 Not Found response be the sent RequestURI?
Please see below for the detail:
Best regards
1 REPLY 1
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Email to a Friend
- Report Inappropriate Content
13-12-21 01:23 PM
@HongJooChoi,
There are a couple of ways to inspect the request. The easiest is probably to just enable the Request Data Output parameter on the Web API definition. To do that:

After you do that, you'll need to create the data item in your test process.
An alternative way to inspect the request is to use an external tool like Fiddler to capture the request.
My guess is that the 404 error you're receiving is due to either the Team ID or Channel ID you've passed in is incorrect.
Cheers,
Eric
There are a couple of ways to inspect the request. The easiest is probably to just enable the Request Data Output parameter on the Web API definition. To do that:
- Go to System -> Objects -> Web API Services
- Open the Microsoft Graph - Teams service definition.
- Click on the Send Channel Message action.
- Check the box next to Enable Request Data Output Parameter.
After you do that, you'll need to create the data item in your test process.
An alternative way to inspect the request is to use an external tool like Fiddler to capture the request.
My guess is that the 404 error you're receiving is due to either the Team ID or Channel ID you've passed in is incorrect.
Cheers,
Eric
