> 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-solvio-beta/ticket-type.md).
# Ticket type
A **ticket type** says what kind of request a ticket is — an incident, a question, a change. Types are defined per tenant, identified by their `name`, and ordered for display by `position`.
They are seeded when a tenant is created and are read-only over the API for now.
## List ticket types
> Returns the tenant's ticket types — what kind of request a ticket is. \`position\` is the order they\
> are meant to be shown in.\
> \
> \*\*Filterable and sortable\*\* — \`name\`, \`displayName\`, \`position\`, \`autoAssign\`, \`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":"A **ticket type** says what kind of request a ticket is — an incident, a question, a change. Types are\ndefined per tenant, identified by their `name`, and ordered for display by `position`.\n\nThey are seeded when a tenant is created and are read-only over the API for now.\n","name":"ticket_type"}],"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.ListTicketTypesResponse-domain_TicketType":{"properties":{"count":{"type":"integer"},"data":{"items":{"$ref":"#/components/schemas/domain.TicketType"},"type":"array","uniqueItems":false}},"type":"object"},"domain.TicketType":{"properties":{"assignmentContext":{"type":"string"},"autoAssign":{"description":"AutoAssign / AssignmentContext gate AI ticket-type classification, mirroring DisplayName.\nRead-only today: ticket types are seeded and have no create/patch surface yet, so both\nstay at their defaults until that surface lands.","type":"boolean"},"createdAt":{"format":"date-time","type":"string"},"displayName":{"type":"string"},"name":{"type":"string"},"position":{"type":"integer"},"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-types":{"get":{"description":"Returns the tenant's ticket types — what kind of request a ticket is. `position` is the order they\nare meant to be shown in.\n\n**Filterable and sortable** — `name`, `displayName`, `position`, `autoAssign`, `createdAt`,\n`updatedAt`.\n\nThe list is read-only; the entries are seeded with the tenant.\n","operationId":"listTicketTypes","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.ListTicketTypesResponse-domain_TicketType"}}},"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 ticket types","tags":["ticket_type"]}}}}
```
---
# 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://hub.equipme.io/development/api-reference-solvio-beta/ticket-type.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.