Error Accessing Payments API in Power Automate

James Belich

I'm attempting to use the "Send an HTTP Request" to access to Payments API in Power Automate, but I'm receiving error "404 Resource Not Found."

Using the Sky API Console ("Try It" on the Payments API reference) I was able to find our Payment Transaction ID. I then tried the GET Disbursement List action in the Sky API console. That was successful and the output lists all the disbursements since we started using BBMS.

However, any attempts to access the Payments API using the Send HTTP Request action in PA result in the "404 Resource Not Found" error.

Here's an example of the action in PA:

And here's what I get in the output:

Since everything works in the Sky API Console, the issue clearly lies in PA, but I'm not clear if this is a permissions issue, if I have something incorrect in the Send HTTP Request action, or what.

@Erik Leaver , tagging you since you helped me narrow this down to PA yesterday,

Ben Regier

Two quick changes you'll want to make.

First, the Relative path URL should only be the part of the URL that comes after "blackbaud.com". In your case, you should change that to "/payments/v1/disbursements".

Second, you can't pass query parameters in the relative path field, so remove the "?payment_configuration_id=###" from your URL and put that information in the Query parameters section instead.

James Belich

Thank you @Ben Regier , I'd forgotten about needing to use the relative path. I've updated that and put the payment configuration ID in the query parameters.

So now I'm getting a 401 error: "Access denied due to invalid subscription key. Make sure to provide a valid key for an active subscription." I assume this means I'm not passing in the subscription key correctly (I did double check that I'm using one of the keys for the Payments API and not the Standard API).

I'm passing in the subscription key through the headers (which is how the Sky API console seems to do it):

I'm guessing though that this might not be the right way to do this based on the error I'm getting.

Ben Regier

The Blackbaud connector handles all the authorization and subscription parts of the call for you, so you should be able to remove your headers from the HTTP action and try it again.

James Belich

I get the same 401 error about an invalid subscription key even if I remove the headers, so it's clearly not getting the correct key, but I'm not clear on where in the process that takes place. I'll keep playing around with it.

Ben Regier

The Blackbaud HTTP action does have some restrictions on which APIs it can call. I wonder if Payments is one of the APIs that is not allowed. I've used the HTTP action quite extensively and have never had to enter my subscription key in the headers, so I think the error message you're seeing is misleading. I would guess that Payments are outside the scope of this action.

James Belich

From other threads it seems like at least some people are able to call the Payments API (although I guess I can't be sure they're trying to do so through Power Automate).

@Erik Leaver , is this something you can answer? Is the Payments API accessible through PA's Send HTTP Request action?

Erik Leaver

@James Belich I'm looking to confirm the http access but I'm almost certain that you can't call the payments APIs from it.

Teaser: There will be a related announcement at bbdevdays that should create a pathway forward.