>>

Get User

This route does not require a valid Authorization header, however it is preferred to provide it.

GET/users/<identifier>

Get a user using a User Identifier.

This does not require authorization when not using @me, but authorized users will get a separate rate limit which is usually (hopefully) higher than the guest rate limit.

>>

Path Params
NameType
identifierUserIdentifier
>>

Response

200User

FieldTypeDescription
idNumberThe user’s ID.
usernameStringThe user’s username. This field has to be between 2 and 32 characters long.
display_name?StringThe user’s display name. This field has to be between 2 and 32 characters long.
social_creditNumberThe user’s social credit score.
statusStatusThe user’s status.
bio?StringThe user’s bio. The upper limit is the instance’s Instance Info bio_limit.
avatar?NumberThe user’s avatar. This field has to be a valid file ID in the “avatar” bucket.
banner?NumberThe user’s banner. This field has to be a valid file ID in the “banner” bucket.
badgesNumberThe user’s badges as a bitfield.
permissionsNumberThe user’s instance-wide permissions as a bitfield.
email?StringThe user’s email. This is only shown when the user queries their own data.
verified?BooleanThe user’s verification status. This is only shown when the user queries their own data.
>>

Example

 
curl \
  -H "Authorization: <token>" \
  https://api.eludris.gay/users/@me

{
  "id": 48615849987333,
  "username": "yendri",
  "social_credit": 0,
  "badges": 0,
  "permissions": 0
}