> For the complete documentation index, see [llms.txt](https://hub.equipme.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.equipme.io/development/api-reference-app/priority.md).
# Priority
**Priority** says what to work on first. Levels are defined per tenant, identified by their `name` and ranked by `level`.
A priority is normally not chosen but derived: when a ticket's impact or urgency changes and both are then set, the priority is resolved from the tenant's impact × urgency matrix. Setting `priorityName` on a ticket overrides that, and the chosen priority is left alone as long as neither axis is touched again.
## List priorities
> Returns the tenant's priorities — what to work on first. \`level\` ranks them, the higher the more\
> important; seeded as \`low\` (1), \`medium\` (2), \`high\` (3) and \`critical\` (4).\
> \
> A ticket's priority is normally resolved from its impact and urgency rather than chosen directly.\
> \
> \*\*Filterable and sortable\*\* — \`name\`, \`displayName\`, \`level\`, \`color\`, \`createdAt\`, \`updatedAt\`.\
> \
> The list is read-only; the entries are seeded with the tenant.
```json
{"openapi":"3.1.0","info":{"title":"Solvio REST API","version":"1.0.0-beta"},"tags":[{"description":"**Priority** says what to work on first. Levels are defined per tenant, identified by their `name` and\nranked by `level`.\n\nA priority is normally not chosen but derived: when a ticket's impact or urgency changes and both are\nthen set, the priority is resolved from the tenant's impact × urgency matrix. Setting `priorityName`\non a ticket overrides that, and the chosen priority is left alone as long as neither axis is touched\nagain.\n","name":"ticket_priority"}],"servers":[{"description":"The host serving this document","url":"/api"}],"security":[{"BearerAuth":[]},{"ApiKeyAuth":[]}],"components":{"securitySchemes":{"BearerAuth":{"description":"Token issued by the central equipme authentication, sent as `Bearer `.","scheme":"bearer","type":"http"},"ApiKeyAuth":{"description":"Static key for machine-to-machine access. Alternative to BearerAuth.","in":"header","name":"X-API-Key","type":"apiKey"}},"schemas":{"v1.ListTicketPrioritiesResponse-domain_TicketPriority":{"properties":{"count":{"type":"integer"},"data":{"items":{"$ref":"#/components/schemas/domain.TicketPriority"},"type":"array","uniqueItems":false}},"type":"object"},"domain.TicketPriority":{"properties":{"color":{"type":"string"},"createdAt":{"format":"date-time","type":"string"},"displayName":{"type":"string"},"level":{"type":"integer"},"name":{"type":"string"},"updatedAt":{"format":"date-time","type":"string"}},"type":"object"},"middleware.ErrorResponse":{"properties":{"error":{"$ref":"#/components/schemas/middleware.ErrorBody"}},"type":"object"},"middleware.ErrorBody":{"properties":{"code":{"description":"Code is the stable, machine-readable reason. Clients match on this, not on the message.","type":"string"},"details":{"description":"Details carries structured context where an error has any — a conflict names what it\ncollided with. Absent otherwise."},"message":{"type":"string"}},"type":"object"}}},"paths":{"/v1/ticket-priorities":{"get":{"description":"Returns the tenant's priorities — what to work on first. `level` ranks them, the higher the more\nimportant; seeded as `low` (1), `medium` (2), `high` (3) and `critical` (4).\n\nA ticket's priority is normally resolved from its impact and urgency rather than chosen directly.\n\n**Filterable and sortable** — `name`, `displayName`, `level`, `color`, `createdAt`, `updatedAt`.\n\nThe list is read-only; the entries are seeded with the tenant.\n","operationId":"listTicketPriorities","parameters":[{"description":"JSON filter expression","in":"query","name":"filter","schema":{"type":"string"}},{"description":"Free-text term — no effect here","in":"query","name":"search","schema":{"type":"string"}},{"description":"Comma-separated field:direction terms","in":"query","name":"sort","schema":{"type":"string"}},{"description":"Selection of fields and relations","in":"query","name":"fields","schema":{"type":"string"}},{"description":"Number of entries to skip","in":"query","name":"offset","schema":{"default":0,"type":"integer"}},{"description":"Page size, 1 to 100","in":"query","name":"limit","schema":{"default":100,"type":"integer"}}],"responses":{"200":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/v1.ListTicketPrioritiesResponse-domain_TicketPriority"}}},"description":"OK"},"400":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/middleware.ErrorResponse"}}},"description":"Bad Request"},"401":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/middleware.ErrorResponse"}}},"description":"Unauthorized"},"403":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/middleware.ErrorResponse"}}},"description":"Forbidden"},"500":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/middleware.ErrorResponse"}}},"description":"Internal Server Error"}},"summary":"List priorities","tags":["ticket_priority"]}}}}
```
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://hub.equipme.io/development/api-reference-app/priority.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.