400 Error on User Create POST

Lindsey Bryant

Has anyone been able to successfully execute the POST for User Create recently? I tried yesterday and today, and I keep getting a 400 errors. I did switch the “nickname” over to “preferredname” as that was a recent change, but nothing seems to be working:

{

"deceased": false,

"dob": "",

"email": "testing@gmail.com",

"email_active": true,

"first_name": "Testing",

"host_id": "0123456",

"last_name": "Testing",

"lost": false,

"maiden_name": "",

"middle_name": "V",

"preferred_name": "",

"prefix": "Mr.",

"suffix": ""

}

Stephen Boyle

@Lindsey Bryant
This was reported by another client as well. So, we have fixed it and it will be in the 10/31 release.

Lindsey Bryant

@Stephen Boyle thanks for the update and I'm glad to hear it will be fixed.

I do want to ask a couple of follow up questions. What was the issue and is there a process in place to minimize this critical API from being broken in the future? For us, if this would happen during beginning of March, this could have huge implications for our school enrollment. We want to have confidence in the APIs and leverage them, but situations like this start to cause concern. Thanks for any insight you can provide.

Stephen Boyle

@Lindsey Bryant
We recently updated the User Post and Patch significantly. That in itself is unusual, as we typically do not need to go back to existing endpoints like that. In this case, while it seemed straightforward, it uncovered some long-standing issues in the endpoints. Now that they are back to a stable place, these endpoints won't see any additional work. If there is any reason to revisit them in the future, we will build a completely new endpoint to avoid this very issue.

Lindsey Bryant

@Stephen Boyle I did want to share that even though I got a 400 error, it did still create the record. I'm not sure if that's something you or your team is aware of. Thanks!