Create subscription API in Microsoft Graph fails to validate incorrect notification url

Question

Create subscription API in Microsoft Graph fails to validate incorrect notification url

Chetna Agrawal 5

I am passing incorrect notification url in create subscription request, and response is 201 "Created", where ideally it should fail and return 400 "Bad Request". Steps to reproduce the behavior Fire create subscription API via postman: Url - https://graph.microsoft.com/v1.0/subscriptions
Request Type - POST
Body -
{
"changeType": "created",
"notificationUrl": "https://webhook.azurewebsites.net/api/send/myNotifyClient",
"resource": "me/mailFolders('Inbox')/messages",
"expirationDateTime":"2016-11-20T18:23:45.9356913Z",
"clientState": "secretClientValue",
"latestSupportedTlsVersion": "v1_2"
}

Sourabh Gupta 800 Reputation points Microsoft External Staff

2024-03-02T13:30:46.96+00:00

Hi Chetna Agrawal. There might be some exceptions with graph explorer and postman. The notificationUrl might not be verified. Could you please try it with code and running it on local host by configuring ngrok as mentioned at following documentation.

https://learn.microsoft.com/en-us/samples/microsoftgraph/nodejs-webhooks-sample/microsoft-graph-webhooks-sample-for-nodejs/
Chetna Agrawal 5 Reputation points

2024-03-04T05:41:03.2333333+00:00

Hi Sourabh,

Thanks for your reply. We have a web application in which we are using microsoft-graph jar for using graph apis. We recently upgraded that jar from 5.59.0 to 6.3.0. The notification url needs to be validated, as it was happening with older version of graph jar.
Sourabh Gupta 800 Reputation points Microsoft External Staff

2024-03-04T16:05:19.65+00:00

Hi Chetna,

Is the subscription getting created successfully from your application even when the notification url is not validated?
Chetna Agrawal 5 Reputation points

2024-03-04T16:07:47.9666667+00:00

Yes, that is exactly what is happening.
Sourabh Gupta 800 Reputation points Microsoft External Staff

2024-03-04T16:11:18.7466667+00:00

Could you please share the code you have at your notification end point?.. do you receive notifications as well after the subscription is created successfully ?
Sourabh Gupta 800 Reputation points Microsoft External Staff

2024-03-04T16:25:06.6166667+00:00

Are you receiving notifications corresponding to that particular subscription?
Chetna Agrawal 5 Reputation points

2024-03-12T11:41:35.8466667+00:00

Hi Sourabh,

It seems that the issue is fixed now. For the invalid notification url, we are getting expected error.

Thanks.

Your answer

Sourabh Gupta 800 Reputation points Microsoft External Staff

2024-03-02T13:30:46.96+00:00

Hi Chetna Agrawal. There might be some exceptions with graph explorer and postman. The notificationUrl might not be verified. Could you please try it with code and running it on local host by configuring ngrok as mentioned at following documentation.

https://learn.microsoft.com/en-us/samples/microsoftgraph/nodejs-webhooks-sample/microsoft-graph-webhooks-sample-for-nodejs/
Chetna Agrawal 5 Reputation points

2024-03-04T05:41:03.2333333+00:00

Hi Sourabh,

Thanks for your reply. We have a web application in which we are using microsoft-graph jar for using graph apis. We recently upgraded that jar from 5.59.0 to 6.3.0. The notification url needs to be validated, as it was happening with older version of graph jar.
Sourabh Gupta 800 Reputation points Microsoft External Staff

2024-03-04T16:05:19.65+00:00

Hi Chetna,

Is the subscription getting created successfully from your application even when the notification url is not validated?
Chetna Agrawal 5 Reputation points

2024-03-04T16:07:47.9666667+00:00

Yes, that is exactly what is happening.
Sourabh Gupta 800 Reputation points Microsoft External Staff

2024-03-04T16:11:18.7466667+00:00

Could you please share the code you have at your notification end point?.. do you receive notifications as well after the subscription is created successfully ?
Sourabh Gupta 800 Reputation points Microsoft External Staff

2024-03-04T16:25:06.6166667+00:00

Are you receiving notifications corresponding to that particular subscription?
Chetna Agrawal 5 Reputation points

2024-03-12T11:41:35.8466667+00:00

Hi Sourabh,

It seems that the issue is fixed now. For the invalid notification url, we are getting expected error.

Thanks.

Share via

Create subscription API in Microsoft Graph fails to validate incorrect notification url

Your answer