current_status field in admissions/candidates endpoint

Dan Bonville

Hello,

We recently updated some of our error logging which shed light on something that has been happening, though we didn't expect it.

Basically, when querying admissions/candidates, we started seeing candidates that lacked a current_status field.

We didn't anticipate this when building our integration behaviors, so it was causing a (relatively painless) issue on our end. We'd like to handle this better so I was wondering if anyone could help me with a few questions:

• Is this expected? The documentation for that endpoint does list that field as nullable in the schema, but it also lacks user_id as nullable, so I wasn't sure I could trust that 100%
• What is the scenario where a user would lack a current_status? Is it as simple as they have not been assigned one?

Thanks for any help anyone can provide.

Dan

Jess Moxsky

If a candidate has not yet been assigned a checklist, they will not have a status.