Restrictions in login email characters

when getting a user using a email that contains a “#” character I get a 400 Bad request"

example:
curl --request GET --url https://spacelysprokets.okta.com/api/v1/users/#George.Jetson@gmail.com --header ‘accept: application/json’ --header ‘authorization: SSWS downwithcogswellcogs’ --header ‘cache-control: no-cache’ --header ‘content-type: application/json’

400 Bad Request

Bad Request

Your browser sent a request that this server could not understand.

Is there a restriction on what character can be used in an email?

We support rfc5322 email addresses. Fragments are typically not sent in HTTP Requests so you shouldn’t be getting a 400 in that case as it would just drop the fragment and list all users.

1 Like