VSO Webhook now failing 403 Forbidden

Ben 's Avatar


10 May, 2021 10:24 AM


This morning our VSO webhook has started receiving a 403 from the https://ci.appveyor.com/api/vso/webhook?id= endpoint. Nothing has changed on the VOS side and the webhook has been working for years before this.

Am I missing something obvious or has something changed?



  1. 1 Posted by Ben on 10 May, 2021 10:42 AM

    Ben 's Avatar

    I got it sorted out. I found the following AppVeyor email:

    AppVeyor uses OAuth to access Azure DevOps resources. Azure DevOps removed obsolete authorization scopes from OAuth flow which broke the integration with AppVeyor. As a result some AppVeyor customers were unable to login with VSTS button or start new builds with VSTS repositories.
    We deployed a fix and the customers should be able to re-authorize Azure DevOps on either "New project" or "Account > Authorization" pages. Unfortunately, we were unable to keep original OAuth app registration and had to create a new one, because scopes of existing app registration cannot be updated.



  2. Support Staff 2 Posted by Feodor Fitsner on 10 May, 2021 03:17 PM

    Feodor Fitsner's Avatar

    Hi Ben,

    Thanks for the update and sharing the solution here.

  3. Feodor Fitsner closed this discussion on 10 Jul, 2021 09:03 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac