Small and medium business | Business Central, N...

Deleting/Updating a webhook subscription using v2 API

(2) Share

Report

Posted on by NS-27040924-0

Hi,

I am using Business Central v2.0 API to create/delete/renew webhook subscriptions for a custom app in our organization. Although create works fine and I can see my subscriptions in GET subscriptions API response, DELETE and PATCH(renew subscriptions) fail with HTTP 404 error with /Bad Request - Error in query syntax/ as seen below:

I'm following this doc and setting the subscriptionId in DELETE API from the output of GET API response. Also I've copied the @odata.etag value from output of GET API response and used that in the value of `If-Match` header in DELETE and PATCH API requests.

I have used the value of the @odata.etag value as is, unescaped the quotes as documented in a similar post for v1 API and tried various other combinations as well but the error persists.

This is the output of my GET subscriptions response:

I send a DELETE on this URL /https:/api.businesscentral.dynamics.com/v2.0/production/api/v2.0/subscriptions(d2fc1f47490b4124afaf53523931dcf9)/ with If-Match header value set to

Parts of the docs are inconsistent as here they ask to use the v2.0 API for PATCH/DELETE but here they suggest using v1.0 API even though both are v2 reference docs.

Has anyone been able to get this working? Appreciate any pointers on this!

Thanks

Nitesh

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (2)

Answers (0)

Sort by

Suggested answer

CT-12061724-0 6 on at

Like (2)

Report
Copy link

Link copied!

The subscription PATCH request to renew needs to have single apostrophes in the URL, which is not consistent:

BAD = api/v2.0/subscriptions(d2fc1f47490b4124afaf53523931dcf9)

GOOD = api/v2.0/subscriptions('d2fc1f47490b4124afaf53523931dcf9')

The header needs a valid If-Match, which can either be the latest etag or simply *, so If-Match="*"

The payload must include the clientState (if you provided one when creating the subscription) and the resource, so for the generalLedgerEntries subscription:

{
"clientState": "theClientStateYouSet",
"resource": "api/v2.0/companies(company_id)/generalLedgerEntries"
}

Was this reply helpful? Yes No
Suggested answer

Sohail Ahmed 11,175 Super User 2026 Season 1 on at

Like (1)

Report
Copy link

Link copied!
The HTTP 404 / Bad Request error when deleting/patching webhook subscriptions via BC v2.0 API, despite successful creation, often points to:

Incorrect @odata.etag format in If-Match header: Ensure it's exact, including quotes (e.g., "W/\"...").

subscriptionId formatting in URL: Verify no extra characters or incorrect encoding.

API Version Inconsistency/Bug: Consider trying the v1.0 webhook endpoint for DELETE/PATCH if v2.0 fails consistently, as there are known inconsistencies.

The "Error in query syntax" strongly suggests a formatting issue with the ID or ETag.

✅ Mark this answer as verified if it helps you.

Was this reply helpful? Yes No

Join the conversation

Community site session details

Deleting/Updating a webhook subscription using v2 API

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Meet the Microsoft Dynamics 365 Contact Center Champions

Congratulations to the April Top 10 Community Leaders

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates

Community site session details

Deleting/Updating a webhook subscription using v2 API

Helpful resources

Quick Links

Introducing the 2026 Season 1 community Super Users

Meet the Microsoft Dynamics 365 Contact Center Champions

Congratulations to the April Top 10 Community Leaders

Subscribe to this forum!

Select categories

Leaderboard > Small and medium business | Business Central, NAV, RMS

Featured topics

Product updates