-
Addition of Communication Preference List (All constituents) entity
With the new Consents module's arrival and GDPR approaching, we'd like to be able to do some detailed reporting on Solicit Codes/Communication Preferences via the API. Without an Communication Preference List (All constituents) entity, we have to ...2
-
Allow addition of Table Entries (Look ups) through the API
Where the SKY API is being used to synchronise NXT with another system (e.g. student records) we have to accommodate the scenario that new, validated values that would appear in a table entries / look up (e.g. Degree Name, Scholarship Name) need t...3
-
Address Info source field and Phone Comment field are not accessible via SKY AP.
We would like to have the Address Info source field in the address API and Phone Comment field in the Phone API which are currently not accessible via SKY AP. We are working on Student Records System and the Raiser's Edge integration via Sky AP...2
-
Add a Membership list (All Constituents) to the SKY Constituent API
This is an obviously missing piece of functionality. There is already a Membership List (Single constituent) call and a lot of other (All constituents) calls but this one is missing.3 Planned
-
Additional endpoints for Prospect Status field
Currently GET is the only end point available for Prospect Status. For the purpose of tracking prospect management cycle it would be beneficial to have access to POST, PATCH, and DELETE as well.0
-
Constituent record needs "ethnicity"
Bio 2 has a field for Ethnicity, but it is not available in the API.1
-
Enable Action Notes through Constituent API
The request is for GET/POST/PATCH/DELETE of notes on actions. This is the only data on the action entity that is in the user interface but not available on the action entity. Further, since one note is already exposed via the description fiel...0
-
'requests_no_email' property on Constituent entity
Raiser's Edge NXT Database View has a Requests no email flag on constituent records. It'd be valuable for the Constituent API to include this as an editable property on the Constituent entity.
0
-
Allow additional end points through the API
Import ID, Edcation Import ID and Education Attributes2
-
Adding Gift Matching info (General 2 tab) to the relationship record and Constituent API
General 2 tab from the database view is not available on the relationship record in the web view and in Constituent API.