---
title: "Get Priorities"
method: GET
path: "/v2/priorities"
tags: ["Routes", "Priorities"]
---

# Get Priorities

`GET /v2/priorities`

This request returns your priorities in Limble. 

Return data description

Property: priorityID, Description: The priority's unique identifier.
Property: name, Description: The full name of the priority.
Property: priorityLevel, Description: A number representing ordering or indicator of severity.
Property: color, Description: A hex-color string that will be used to color tasks associated to this priority.
Property: isDefault, Description: A boolean representing whether or not this is the priority that will be associated to tasks by default.

## Query parameters

- `priorities` integer

## Response `200`

Get Priorities

- object[]
  - `priorityID` integer
  - `name` string
  - `priorityLevel` integer
  - `color` string, color
  - `isDefault` boolean

## 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.
- `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/revisions/eceb9442ed4d/schema)