---
title: "Get User Roles"
method: GET
path: "/v2/users/{userID}/roles"
tags: ["Routes", "Users", "Roles"]
---

# Get User Roles

`GET /v2/users/{userID}/roles`

This request gets all of the Roles a User has and what Location they have that Role at.

## Query parameters

- `roles` string
- `locations` string
- `name` string
- `cursor` integer
- `limit` integer

## Response `200`

Get User Roles

- object[]
  - `roleID` integer
  - `locationID` integer
  - `name` string

## Other responses

- `400` — The request was malformed — either invalid JSON syntax or a validation failure (missing required field, wrong type, etc.).
- `401` — No `Authorization` header was provided on the request.
- `403` — The supplied credentials are invalid, the customer account is inactive, or the credentials do not have permission to perform this action.
- `404` — The referenced resource does not exist or is not visible to the authenticated customer.
- `429` — The per-minute or per-hour rate limit for this credential and method has been exhausted. Inspect the `X-RateLimit-*` headers to determine when to retry.
- `500` — An unhandled server-side error. The body message is generic (`System unavailable...`) when the underlying cause is a database fault; otherwise it reflects the raised error.

---

[API](https://skmtc.net/limblecmms/apis/limble-api-v2.md) · [All operations](https://skmtc.net/limblecmms/apis/limble-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/limblecmms/limble-api-v2/versions/20801e23f7f2/schema)
