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?

Best Answer

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

    I am now able to receive OPTIONS calls in my HTTP flows, and have been able to resubscribe all of my webhooks to my flows using the new flow URLs.

    The new flow URLs are longer than 255 characters, which causes problems as many webhooks have a 255 character limit on the URL, but luckily Blackbaud does not seem to have that restriction.

Answers

Categories