Hi Everyone, We have a project to update Fund IDs. Currently, there is no API for updating the Fund ID in this endpoint: https://developer.sky.blackbaud.com/api#api=58bdd6c8d7dcde06046081d7&operation=GetAppeal However, Glen from the community suggested using the “Update fund” API under Data Integration: https://developer.sky.blackbaud.com/api#api=nxt-data-integration&operation=EditFund I’ve tried calling the Data Integration API multiple times, but I consistently receive a 403 Forbidden response. I have a few questions: * What is the difference between these two API documentations/endpoints? * Is anyone currently using the Data Integration APIs are they working for you? * Are there any specific permissions or configuration settings required in the environment to use the Data Integration APIs? I opened a support ticket regarding the 403 Forbidden error, but I have not received clear guidance. As of today, when I use the “Try it” option on the API page, I get a 503 Service Temporarily Unavailable response, and when I call the API from Power Automate, I still receive a 403 Forbidden error. Any insight or examples from others who have successfully used the Data Integration API's would be greatly appreciated. Thank you!

Hi @Venky Immadisetty , a couple of things to check / eliminate as possibilities: * Refer to the top part of the NXT Data Integration resources and confirm you have the right permissions. * Verify that the paramaters you're sending over to it are accurate for your setup. For instance, the values in the example given in the Documentation for the likes of fund_category_id, campaign_id, default_appeal_id, etc are simply example values and may not be valid for every installation. If your Appeal ID 17 has been deleted (or you never had that many appeals), that may be one reason for an error. [Update] I did a test and was able to make updates to a Fund using the NXT Data Integration endpoint without having to supply all of the fields in the example. What this means is that if your goal is focused on updating the Fund ID then in your processing and testing, all you need to do is include the "fund_id" field.

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Unable to Use Data Integration EditFund API (403 Forbidden)

Venky Immadisetty

Hi Everyone,

We have a project to update Fund IDs. Currently, there is no API for updating the Fund ID in this endpoint: https://developer.sky.blackbaud.com/api#api=58bdd6c8d7dcde06046081d7&operation=GetAppeal

However, Glen from the community suggested using the “Update fund” API under Data Integration: https://developer.sky.blackbaud.com/api#api=nxt-data-integration&operation=EditFund

I’ve tried calling the Data Integration API multiple times, but I consistently receive a 403 Forbidden response. I have a few questions:

What is the difference between these two API documentations/endpoints?
Is anyone currently using the Data Integration APIs are they working for you?
Are there any specific permissions or configuration settings required in the environment to use the Data Integration APIs?

I opened a support ticket regarding the 403 Forbidden error, but I have not received clear guidance. As of today, when I use the “Try it” option on the API page, I get a 503 Service Temporarily Unavailable response, and when I call the API from Power Automate, I still receive a 403 Forbidden error.

Any insight or examples from others who have successfully used the Data Integration API's would be greatly appreciated.

Thank you!

Find more posts tagged with

Microsoft Power Platform

Accepted answers

Glen Hutson

Hi @Venky Immadisetty , a couple of things to check / eliminate as possibilities:

Refer to the top part of the NXT Data Integration resources and confirm you have the right permissions.
Verify that the paramaters you're sending over to it are accurate for your setup. For instance, the values in the example given in the Documentation for the likes of fund_category_id, campaign_id, default_appeal_id, etc are simply example values and may not be valid for every installation. If your Appeal ID 17 has been deleted (or you never had that many appeals), that may be one reason for an error.

[Update] I did a test and was able to make updates to a Fund using the NXT Data Integration endpoint without having to supply all of the fields in the example. What this means is that if your goal is focused on updating the Fund ID then in your processing and testing, all you need to do is include the "fund_id" field.

All comments

Erik Leaver

Can you share the sample request body in the TryIt that's providing the 503 error? There are a number of required fields.

Venky Immadisetty

@Erik Leaver,
I am passing the Fund System Record as a parameter

and below request body
{
"fund_id": "20ANNUAL",
"description": "2020 Annual Fund",
"fund_category_id": 70,
"fund_type_id": 42,
"campaign_id": 1,
"start_date": "0001-01-01T12:00:00Z",
"end_date": "0001-01-01T12:00:00Z",
"inactive": false,
"default_appeal_id": 17,
"notes": "Notes for the annual fund.",
"goal": 100000,
"restricted": false
}

Thanks!

Glen Hutson

Hi @Venky Immadisetty , a couple of things to check / eliminate as possibilities:

Refer to the top part of the NXT Data Integration resources and confirm you have the right permissions.
Verify that the paramaters you're sending over to it are accurate for your setup. For instance, the values in the example given in the Documentation for the likes of fund_category_id, campaign_id, default_appeal_id, etc are simply example values and may not be valid for every installation. If your Appeal ID 17 has been deleted (or you never had that many appeals), that may be one reason for an error.

Venky Immadisetty

Thanks @Glen Hutson, I followed the community post instructions to gain access. I can now access the NXT Data Integration API successfully

https://community.blackbaud.com/discussion/81737/introducing-new-nxt-data-integration-api-permissions