Users: your own account's members, or for staff any account's (a role needs an account)
GET
/v1/users
const url = 'https://api.tallyray.com/v1/users?sort=email';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://api.tallyray.com/v1/users?sort=email' \ --header 'Authorization: Bearer <token>'Who: a signed-in user, not an API key. Not for API keys.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”page_size
integer
Rows a page, up to the list’s maximum; the service’s default when left out
page_token
string
The previous page’s meta.next_page_token
sort
string
Comma-separated fields, each with - for descending
account
string
role
string
status
string
q
string
Responses
Section titled “Responses”OK
Media typeapplication/json
object
data
required
Array<object>
object
created_at
required
string format: date-time
created_by
required
email
required
string
email_verified_at
required
string | null format: date-time
id
required
string
last_signed_in_at
required
string | null format: date-time
name
required
string
status
required
string | null
time_zone
required
string
updated_at
required
string format: date-time
meta
required
object
next_page_token
required
string | null
total
required
integer | null format: int64
total_approximate
required
boolean
Example
{ "data": [ { "created_by": { "kind": "user" }, "status": "invited" } ]}default
Section titled “default”An error: its code, a message, and the fields at fault
Media typeapplication/json
object
error
required
object
code
required
string
fields
object
key
additional properties
string
message
required
string
Example generated
{ "error": { "code": "example", "fields": { "additionalProperty": "example" }, "message": "example" }}