---
title: "New Priority"
method: POST
path: "/v2/priorities"
tags: ["Routes", "Priorities"]
---

# New Priority

`POST /v2/priorities`

This request creates a new Priority.

When providing priorityLevel or isDefault, calls to this endpoint may reorder or otherwise adjust other priorities.

Parameter: name, Type: String, Required?: Required, Description: The title of this priority.
Parameter: priorityLevel, Type: Int, Required?: Required, Description: What level is this priority? If we're inserting a priority in the middle of the levels, priorities with a priorityLevel equal-to or greater-than the specified priorityLevel will have their priorityLevel incremented by one. This can only be between the numbers 1 and the current highest priorityLevel + 1.
Parameter: color, Type: String, Required?: Optional, Description: This is the color that will be shown on all tasks with this priority. Default is #429b1f
Parameter: isDefault, Type: Boolean, Required?: Optional, Description: Should this be the default priority that tasks are assigned to when a priority is not specified? Default is false. If isDefault is true, then any other priorities will have their isDefault set to false.

## Request body

- object
  - `name` string
  - `priorityLevel` integer
  - `color` string, color
  - `isDefault` boolean

## Response `201`

New Priority

- object
  - `priorityID` integer

## 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.
- `409` — The request conflicts with the current state of the resource (e.g. a uniqueness constraint or a referenced parent that is in the wrong state).
- `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)