New flow HTTP trigger URLs and webhooks

Ben Regier
Ben Regier
Sixth Anniversary Kudos 5 Name Dropper Participant
in SKY Developer General Discussions

As many of you are already aware, Microsoft is changing the URLs for all HTTP triggers. I've been going through and updating my processes, but have run into one hiccup.

I don't seem to be able to subscribe to a SKY API webhook with the new URLs. I'm doing the trick where you set the trigger to receive OPTIONS calls and add a response to let it know the call was successful. (The process is outlined here.)

When I try to subscribe using the Create Subscription endpoint, I get this error message:

Received an invalid HTTPS status code from your webhook URL when performing the CloudEvent's Abuse Protection handshake with your webhook URL. Review our Webhook API documentation to learn more. https://developer.blackbaud.com/skyapi/apis/webhook

To test further, I created another flow and tried to send an OPTIONS call to my webhook flow myself. Even that fails, and I get a routenotfound error, and it tells me that my URL does not match any known API routes.

Is it impossible to use these new URLS for OPTIONS calls (and by extension, webhook subscriptions)? Has anyone else been successful with this?

Answers

  • Alex Wong
    Alex Wong Community All-Star
    Ninth Anniversary Kudos 5 Facilitator 3 Raiser's Edge NXT Fall 2025 Product Update Briefing Badge

    I also posted about this and is waiting for @Ben Wong to assist

    Microsoft Request Trigger - Webhook Change — Blackbaud Community

  • Joel Silva
    Joel Silva
    Third Anniversary Facilitator 1 Blackbaud Certified

    From what I have read, the new HTTPS trigger cannot handle Options calls anymore. A workaround is to use a relay. However, the relay url would be subscribed, not your flow url.

  • Ben Regier
    Ben Regier
    Sixth Anniversary Kudos 5 Name Dropper Participant
    https://community.blackbaud.com/discussion/comment/306756#Comment_306756

    Hmm, that's what I was afraid of. Do you remember where you read about this? I've been having trouble finding good information on these changes.

  • Jason Guan
    Jason Guan
    Second Anniversary Name Dropper Facilitator 1

    Has anyone heard from Blackbaud on what we should be doing going forward?

  • Ben Regier
    Ben Regier
    Sixth Anniversary Kudos 5 Name Dropper Participant

    I haven't heard anything official, no.

    There's a workaround that allows you to get to your query parameters, even though it's a few extra steps.

    As for options calls and subscribing to webhooks, I haven't heard anything yet.

  • Josh Gould
    Josh Gould
    Tenth Anniversary Kudos 1 Name Dropper Participant

    @Ben Regier I went to update my webhooks today and ran into the same error.

    "Received an invalid HTTPS status code from your webhook URL when performing the CloudEvent's Abuse Protection handshake with your webhook URL. Review our Webhook API documentation to learn more. https://developer.blackbaud.com/skyapi/apis/webhook%22

  • Ben Regier
    Ben Regier
    Sixth Anniversary Kudos 5 Name Dropper Participant

    The good news is that the query parameters issue seems to have been fixed.

    Also, if you look at the current list of Known Issues, Microsoft is aware that calls using the HEAD method are not working, and they have said that the old URLS will continue to function until that is fixed.

    I spent some time chatting with Microsoft's support AI last week, and it insists that Microsoft is aware that OPTIONS calls are also not working, and that the old URLS will keep working until this is fixed, just like with the HEAD calls. But I couldn't get it to give me a link to any official documentation that confirms this, so I'm worried it's a hallucination.

    A lot of people seem to be using Azure API Management on Consumption pricing as a workaround.

Categories