API bug? /emergencycontacts/changed only returns ~1,000 emergency contacts, none of them for active students

Eric Eskildsen

@Todd DeSchuiteneer

Todd, I'm seeing what looks like a bug with /emergencycontacts/changed….Could we take a look?

• Steps to reproduce:
  
  GET /emergencycontacts/changed for a school with thousands of alumni/tens of thousands of users.
  
• Expected result:
  
  "All emergency contacts for all users" are returned as per the documentation (link).
  
• Actual result:
  
  Only the first ~1,000 emergency contacts are returned.
  
  Testing with 3 schools, the actual numbers of emergency contacts returned are:
  
  994
  999
  995
  
  For two of the three schools above, the contacts returned seem to be for the first Blackbaud users, sorted by ID ascending. Users with higher numeric IDs (e.g., active students) are not in the list.
  
  That said, I may be misunderstanding the sorting…just trying to provide more context around what I'm seeing in case it helps.

Edit: I should mention too that next_link is blank here.

Todd DeSchuiteneer

Thanks @Eric Eskildsen, I will have a look at this. It may be functioning correctly only returning 1000 results. I do see that you are stopping just short of 1000 though and I think this is due to the fact that the next user in the results would put the count over 1000. Once I have a definite answer I will reply back.

Eric Eskildsen

@Todd DeSchuiteneer Thanks Todd. Usually I would expect pagination here and follow next_link, but that's blank here.

When you say it may be functioning correctly, does that mean it's supposed to (1) paginate at 1,000 users or (2) only return emergency contacts for 1,000 users total?

If #1, it seems like there's an issue as next_link is blank and the “count” property's value is the number of items in the current response array.

If #2, the documentation is inaccurate right now as it says the endpoint returns all emergency contacts for all users.

Todd DeSchuiteneer

@Eric Eskildsen I am going to have my team look into the functionality of the endpoint. I will be reaching out through our existing case to gather a few more details from you.