Pain point · API & developer experience · Annoyance
Create-user endpoints return a vague server error for a null name
2 source threads · first seen 2022-09 · last seen 2024-10
Summary
Sending a null name to the user creation endpoints produces an unhelpful server error although the name is optional. The developer, who is building their own SDK, can work around it.
- Affects
- developer building a custom SDK
- Workaround
- Omit the name field instead of sending null
Evidence
Excerpts are copied word for word from the source; follow the link to read it in full.
“Name is optional anyway, so specifying it as null should not create this error”
“400 error response with some helpful message”