Adding 2 x API end points (Alias and Education Attributes)

This is a key requirement for customers student data flow between RE and their SITS/other system and would help to support a large number of our Higher Ed accounts as well as schools and colleges.

  • Guest
  • Jan 5 2018
APIs
  • Attach files
  • Erik Pearson commented
    June 15, 2021 19:34

    We could really use these. Looks like this was first added in 2018. Any movement on these endpoints?

    Attachments Open full size
  • Christopher Dawkins commented
    March 17, 2019 12:06

    We have the same requirement too. Alias List (All constituents) would be very useful.

    Attachments Open full size
  • Joe Werner commented
    March 01, 2019 21:24

    We have the same requirement. We need to be able to find a constituent by alias.  This is something users can do via the UI already.

    Attachments Open full size
  • Grant Quick commented
    March 16, 2018 17:19

    For our requirements, we would like to see an Alias List (All Constituents) entity, as we use aliases to record IDs from other systems. In order to get a list of Constituent IDs and aliases of a particular type, currently we would have to make an individual call to the Alias list (Single constituent) for every constituent.

    Attachments Open full size
  • Deleted User commented
    March 16, 2018 16:04

    Given that these capabilities do not yet exist in the Raiser's Edge NXT Web View, I don't have a great estimate of when we will be able to include this in the API at this time.

    I would like to better understand your use cases, though. What do you use these attributes for? Are you looking for full CRUD operations on Alias and Education attributes? Or predominately read access?

    Attachments Open full size

Related ideas