975acfd606
* Fixed weird match with get_online_members + Now using special(smoll) Public Member struct for public member data fetches as. They're size on networks should be pretty small so we can package a ton of them in a single request DOCS changes: - Removing references to unix timestamps in seconds - Removing references to joindate * Exact content-type values now specified
37 lines
664 B
Markdown
37 lines
664 B
Markdown
---
|
|
title: Users
|
|
anchor: users
|
|
weight: 50
|
|
---
|
|
|
|
### Personal User
|
|
|
|
If you need to get your own user data, with `/users/me` then the data received on success has the following fields:
|
|
|
|
Name | Type
|
|
:------:|:-----:
|
|
id | `u64`
|
|
secret | `String`
|
|
status | `i32`
|
|
permissions| `u64`
|
|
|
|
### JWT
|
|
|
|
This data is retrieved after a sucessful `/login` hit.
|
|
|
|
Name | Type
|
|
:-----:|:------:
|
|
jwt | `String`
|
|
|
|
### Full Public User
|
|
|
|
Name | Type
|
|
:-----:|:-----:
|
|
id | `u64`
|
|
name | `String`
|
|
status | `i32`
|
|
permissions| `u64`
|
|
|
|
For users _without_ the `USER_FETCH` permission the only two fields with actual data is `id` and `name`. The other fields will be set to 0.
|
|
|