# List staff members

`GET /api/v1/staff-members`

The store's team, newest member first: who is a member, what role each one holds, and whether that membership is active. THIS IS WHAT RESOLVES THE USER IDS THIS API ALREADY HANDS YOU. assigned_to on a conversation and author_user_id on a message are store user ids and nothing else published here could turn one into a person, so an inbox rendering a thread showed a raw identifier. Sync this list once and you can name every actor in it. THE id IS THE USER ID, not a membership id. It is the same value assigned_to carries, the same value the conversation PUT accepts back, and it is stable across stores, because one person can be on more than one team. SUSPENDED AND INVITED MEMBERS ARE INCLUDED. Their ids still appear on conversations and messages you already hold, so hiding them would answer "no such member" for somebody plainly named on the thread you are rendering. Read status before you assign NEW work: only active grants access, so assigning to a suspended member gives it to someone who cannot log in to see it. first_name and last_name are BEST EFFORT and may be null. They come from a second lookup outside the membership record, and a failure there degrades to an unnamed member rather than failing the roster, so the id is always right and the name may be absent. Do not key anything on the name. NO EMAIL ADDRESS IS PUBLISHED. Every consumer of this resource takes a user id, and the address is additionally the input the merchant's own team-invite uses, so serving it here would make this grant a staff mailing list ranked by role. If you need to reach a teammate, do it through the merchant rather than through this API. NO FILTERS. A team is tens of rows, role and status arrive on every one of them, and a query parameter cannot be withdrawn once you have written against it. THIS FAMILY IS READ ONLY and there is no write half to add later. The role field is not an attribute of this resource, it IS the resource, so a write would promote a member, demote an owner, or suspend the one person able to undo either, from a key already acting inside the store. apiscope mints no write_staff at all. Team changes stay in the dashboard, where a human owner makes them.

## Query parameters

- `limit` (integer) — Rows per page. Out of range is a 400 rather than a silent clamp, so a client asking for more than 100 learns it did not get it.
- `after` (string) — The next_cursor from the previous page. Opaque: decode nothing from it and construct nothing by hand, since its encoding is not part of this contract. Omit it to read the first page.

## Responses

- `200` — Success
- `400` — The request was refused before any state changed. `code` is one of:

`invalid_body`, a write body this route will not take. `reason` partitions it
and `field` names the key when one key is at fault.
`invalid_query`, a query parameter, including limit and after.
`invalid_text`, a NUL byte or bytes that are not valid UTF-8 anywhere in the
path, the query or the body. Strip control characters before sending.
`idempotency_key_required`, a write sent without the Idempotency-Key header.
`invalid_request`, an Idempotency-Key longer than 255 bytes.

Routes add their own codes for rules only they know. Switch with a default arm.
- `401` — No credential, or one this API does not accept. `code` is always
`unauthorized`.

THE BODY IS DELIBERATELY UNINFORMATIVE. An expired key, a revoked key, a
publishable key, a key belonging to another merchant and a key that never
existed are all refused with the same bytes, so this response cannot be used to
probe which keys exist. Check the key's state in the dashboard rather than
inferring it here.

Send the key as `Authorization: Bearer <key>` or as `X-API-Key: <key>`. It is
never accepted in a query string.
- `403` — The key lacks the read_staff scope. `code` is `insufficient_scope` and the message names the scope to ask the merchant for.
- `429` — Too many requests. `code` is `rate_limited`.

Two limits apply independently: one on the credential and the route family,
one on the client address. The headers describe whichever has less left, so
honouring Retry-After always clears the window that bound.
- `default` — Any status this operation does not list, in the same envelope.

A 5xx means the request may or may not have applied. Retry it with the SAME
Idempotency-Key: that is the only way to find out without risking a duplicate,
and it is what the key is for.

A few 4xx conditions arrive here rather than as a listed status because they
depend on the merchant's plan or on a module being wired: 402 when a quota or a
plan limit is reached, and 503 when a capability the route needs is not
configured on this deployment. Both carry a `code` naming which.

## Example

```bash
curl --request GET \
  --url 'https://api.mercemur.com/api/v1/staff-members' \
  --header 'Authorization: Bearer <token>'
```