Prospect requirement for Gifts of type pledge in RENXT

Dylan Hochreiter

Hi there,

We currently provide our customers with an integration in our application that gives them the ability to take payments through BBMS as well as create one time and recurring gifts in NXT.

We are working on bringing on a prospect that have a requirement that we do not currently support.

That is the ability to add a Gift of type pledge with installments. Their other requirement is that the pledge gift is added to a batch before it is approved.

After reviewing the APIs, it looks like this isn't available through the V1 Gift API, but it is available in the new V2 Gift API that is in preview mode.

I have a few questions/concerns around using the V2 Gift API.

Since it's in preview mode, the endpoints say “This endpoint is in PREVIEW and may be changed or removed at any time.” I am worried that we build out this integration for the potential prospect and then the API is no longer useable. Is that a valid concern?

Also, I don't see a batch number field for the V2 CreateGift endpoint? Is that something that can still be accomplished somehow? It's available through the V1 endpoint it looks like.

Any and all help with this would be much appreciated.

Thank you,

Dylan Hochreiter

Alex Wong

@Dylan Hochreiter
I'm currently using Gift v2 to create pledge and adding installment to the pledge, this creates the pledge record directly, not into batch first. There is no endpoint to allow for the gift record to be in Batch first, I don't know if there's plan for that.

There is a bug in Add installment API right now, has been there for close to 1 year already, which I'm compensating by having to reschedule the installment in database view right after pledge is created. Blackbaud has not yet delicate resource to fixing this bug, as it is …. in “preview”

Our process requires pledge to be created as part of an automated workflow, the benefits outweight the risk and save our gift entry staff a LOT of time. However, I am the coder of the automation and a staff in the org, so whenever the API endpoint bug is fixed or changes, I can adopt quickly. I can't speak for your situation where you are doing it for a client.

Dylan Hochreiter

Thanks for the info @Alex Wong!