RE NXT Donation Form Sky API

Hi Ben Wong‍ ,


Thanks for the quick reply.  I understand that most organizations have a few donations pages associated with a few funds.  The fundraising model at our organization is built around personal fundraising.  Our 900+ staff each collect donations to their personal support page (currently in Luminate) and those forms are mapped to funds in RE NXT.  Additionally, each year we create  thousands of fundraising pages (each with their own fund ID) to enable them to raise donations towards participation in mission trips.  All of these forms (and donations) are mapped once and synced to RE NXT each night using an application we built internally.  Our model is closer to the legacy Personal Fundraising as opposed to the Team Raiser style in Luminate.  


Looking forward, I would love to have one central CRM (RE NXT) instead of two (RE NXT and Luminate).  We heavily utilize the SKY API (great work on the design!) and I was hoping to have an endpoint to help us generate these types of fundraising pages programmatically.   The constituent match feature for RE NXT donors is very helpful and there are a host of other good reasons to use it.  However, re-creating that many pages (and creating more going forward) is not currently worth the investment.


Happy to explain more if you'd like.


Take care,

Tyler


 

Hi Ben Wong‍ ,


I checked out Just Giving and it does look like it has a helpful tool set.  However, I believe there are two issues:

1. I assume that Just Giving is an additional cost.
2. It looks like the RE NXT integration is only one way.This is the same problem with Luminate and one of the large reasons I'd like to standardize on RE NXT.

The minimum features of the GET Donation Form List would include the following:

Request parameters: None strictly needed.  The typical SKY API ones could be helpful (date_added, last_modified, sort_token, limit, offset).

Response object:

{<br/>  "count": 23,<br/>  "next_link": "https://api.sky.blackbaud.com/donation/v1/forms?offset=1&limit=3",<br/>  "value": [<br/>    {<br/>      "id": "1",<br/>      "form_name": "Super donation form",<br/>      "date_added": "1999-06-25T11:59:57+00:00",<br/>      "date_modified": "2007-06-18T14:44:52.623+00:00",<br/>      "payment_configuration": "2",<br/>      "fund_id": [<br/>        "5235","32423","23432"<br/>      ],<br/>      "appeal_id": "64534",<br/>      "donation_notification": [<br/>        "bob@focus.org","tom@usc.edu","sam@gmail.com"<br/>       ],<br/>      "raised": 893.08,<br/>      "transactions": 4,<br/>      "visits": 14<br/>    },<br/>   { <br/>      "id": "2", <br/>      "form_name": "another great student form", <br/>      "date_added": "1999-06-25T11:59:57+00:00", <br/>      "date_modified": "2009-06-18T14:44:52.623+00:00", <br/>      "payment_configuration": "3", <br/>      "fund_id": [ "1234" ], <br/>      "appeal_id": "", <br/>      "donation_notification": [<br/>        "larry@focus.org"<br/>       ],<br/>       "raised": 1200,<br/>       "transactions": 5,<br/>       "visits": 7<br/>   }<br/> ]<br/>}<br/>

The minimum features of the POST Donation Form would include the following:

  Required Type Description X string The internal name of the form. X string The payment configuration to use for the form.  Available values are the entries in the Payment Configuration List of the Payments endpoint. X array Available values are the entries in the Fund List of the Fundraising endpoint.   string Available values are the entries in the Appeal List of the Fundraising endpoint. X string Available values are the entries in the Donation Form List of the Donation endpoint.   array List of up to 10 email addresses to receive donation confirmation.

Property
form_name
payment_configuration_id
fund_id
appeal_id
template_form_id
donation_notification

The template_form_id would be a proposed work around for the form designer functionality.  When creating a new form with the POST request, the controller would copy the exact same form configuration and confirmation email configuration from the one specified in the template_form_id. This should help keep the endpoint as simple as possible.


Not strictly required, but very helpful, would be POST Fund endpoint.  It seems like a notable exception to the consistent SkyAPI set of endpoints.  Then I could create a fund and the form which references the newly created fund.  


Thank you for considering my request!

Tyler

Hi Ben Wong‍ ,


Thanks for the reply. Ideally, I wouldn't use a template and I would just create the entire form from scratch each time.  I proposed the template idea as a way to simplify the call to create a form.  There is a ton of text, style and other items that would complicate things.  I tried to be mindful of your request to create the smallest possible endpoint that would accomplish the task.


I would be happy to use the donation form API (if and when it comes into existence) without the template.


Tyler

 

Hi Jon Wilson‍ ,


I haven't received any updates from Ben Wong‍ on my original request so I assume the answer is "no."  You and I share a the same problem and a programmatic solution would be most excellent.


Tyler

 

Thank you, ‍ Ben Wong‍ !