> For the complete documentation index, see [llms.txt](https://docs.flowretail.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flowretail.com/docs/developers/api-documentation/service/list-service-job-types.md).

# List service job types

List the tenant's job types — the kinds of work done under a service type, each with the checklist run before handover and the products suggested when the work is priced. Pass serviceTypeUid to list only the job types offered under one service type. Deprecated job types are listed too: they are kept for the service orders that already carry them and are not offered when picking job types. Reading them asks for any service permission — SERVICE\_ORDER or SERVICE\_STORE\_CONFIG at the tenant, at an organization or at any one store, or SERVICE\_CONFIG, which is held at the tenant only — because whoever configures the job types reads them, and the service screens read them to work. A tenant-wide ADMIN grant counts as every permission. A caller holding none of them, a user with no role assignments included, is refused with a 403.

Required permissions: SERVICE\_ORDER, SERVICE\_STORE\_CONFIG, SERVICE\_CONFIG

```json
{"openapi":"3.0.2","info":{"title":"Flow Retail API version 2","version":"2.0.0"},"tags":[{"name":"Service","description":"Service"}],"servers":[{"description":"Flow Retail Production","url":"https://api.flowretail.com/v2"},{"description":"Flow Retail Stage","url":"https://api.stage.flowretail.com/v2"}],"security":[{"accessToken":[]},{"authToken":[]},{"integrationToken":[]}],"components":{"securitySchemes":{"accessToken":{"description":"Access token recevied after user login with a deviceToken","scheme":"bearer","type":"http"},"authToken":{"description":"Token received from the auth service","scheme":"bearer","type":"http"},"integrationToken":{"scheme":"bearer","type":"http"}},"responses":{"ServiceJobTypeListResponse":{"description":"Example response","content":{"application/json":{"schema":{"type":"object","properties":{"items":{"type":"array","items":{"$ref":"#/components/schemas/ServiceJobTypeResponseSchema"}},"paging":{"$ref":"#/components/schemas/Paging"}},"required":["items","paging"]}}}}},"schemas":{"ServiceJobTypeResponseSchema":{"title":"ServiceJobTypeResponseSchema","description":"A job type: the kind of work done under a service type, such as reinstalling the machine under laptop repair. A service order carries one or more job types, and they decide what is checked before it is handed over and what is suggested when the work is priced.\nchecklistItems is the ordered list of tests to run before handover. The checklist is prompted at the transition that ends the work and is either completed with a result for every item or skipped after the user confirms the skip; both outcomes are written on the service order timeline, so the log always answers whether the work was tested. Its items are answered one at a time during the work through put-serviceorders-checklist-answers, and the end-of-work prompt asks only for the items still unanswered.\nEditing a job type never rewrites history: the items and their results are snapshotted on the event when the checklist is submitted.\nA job type is deleted only while it is unused — set deprecated to take it out of use without touching the service orders that already carry it.","type":"object","required":["serviceJobTypeUid","tenantUid","serviceTypeUid","name","checklistItems","suggestedProducts","deprecated","createdAt","createdBy","lastModifiedAt","lastModifiedBy"],"properties":{"serviceJobTypeUid":{"$ref":"#/components/schemas/UID"},"tenantUid":{"$ref":"#/components/schemas/UID"},"serviceTypeUid":{"description":"The service type this job type is offered under. Set when the job type is created and never changes.","type":"string","pattern":"^[A-Za-z0-9-_]+"},"name":{"type":"string","description":"What the work is, as it is shown when picking job types."},"checklistItems":{"type":"array","description":"The tests to run before the service order is handed over, in the order they are prompted in. Empty when the job type has no checklist, in which case nothing is prompted.","items":{"type":"string"}},"suggestedProducts":{"type":"array","description":"The products offered as one-tap additions when the work on this job type is being priced. Empty when the job type suggests none.","items":{"$ref":"#/components/schemas/ServiceJobTypeSuggestedProductResponseSchema"}},"deprecated":{"type":"boolean","description":"A deprecated job type is kept for the service orders that already carry it but is no longer offered when picking job types."},"createdAt":{"type":"string","format":"date-time"},"createdBy":{"type":"string"},"lastModifiedAt":{"type":"string","format":"date-time"},"lastModifiedBy":{"type":"string"}}},"UID":{"title":"UID","type":"string","pattern":"^[A-Za-z0-9-_]+"},"ServiceJobTypeSuggestedProductResponseSchema":{"title":"ServiceJobTypeSuggestedProductResponseSchema","description":"A product offered as a one-tap addition when the work on a job type is being priced, as it is read back. Suggesting a product never puts it on a service order by itself — it only saves the user looking it up when the bill is built.","type":"object","required":["productUid","note"],"properties":{"productUid":{"$ref":"#/components/schemas/UID"},"note":{"type":"string","description":"What the product covers on this job type, shown next to the suggestion so the right one is picked. An empty string when no note was written."}}},"Paging":{"description":"totalCount The total number of items in the result set.\n\npageSize The number of items per page.\n\npageNumber The current page in the result set.","properties":{"pageNumber":{"type":"integer"},"pageSize":{"type":"integer"},"totalCount":{"type":"integer"}},"required":["totalCount","pageSize","pageNumber"],"title":"Paging","type":"object"},"SortDirectionENUM":{"description":"|ENUM      | Description |\n| ---------------- | ------------ |\n| ASC | Sort in ascending order|\n| DESC | Sort in descending order|\n","enum":["ASC","DESC"],"title":"SortDirectionENUM","type":"string"}},"parameters":{"serviceFormServiceTypeUidQuery":{"name":"serviceTypeUid","in":"query","required":false,"schema":{"$ref":"#/components/schemas/UID"},"description":"Filter by service type"},"pageNumberQuery":{"description":"Reference to a specific page in a result set.","in":"query","name":"pageNumber","required":false,"schema":{"type":"integer"}},"pageSizeQuery":{"description":"The number of items per page in a result set.","in":"query","name":"pageSize","required":false,"schema":{"type":"integer"}},"sortByQuery":{"description":"Defines which field the resource list is sorted by.","in":"query","name":"sortBy","required":false,"schema":{"type":"string"}},"sortDirectionQuery":{"description":"Reference to a sort direction","explode":false,"in":"query","name":"sortDirection","schema":{"$ref":"#/components/schemas/SortDirectionENUM"},"style":"form"}}},"paths":{"/tenants/{tenantUid}/serviceorders/jobtypes":{"get":{"summary":"List service job types","tags":["Service"],"responses":{"200":{"$ref":"#/components/responses/ServiceJobTypeListResponse"}},"operationId":"get-serviceorders-jobtypes","description":"List the tenant's job types — the kinds of work done under a service type, each with the checklist run before handover and the products suggested when the work is priced.\nPass serviceTypeUid to list only the job types offered under one service type. Deprecated job types are listed too: they are kept for the service orders that already carry them and are not offered when picking job types.\nReading them asks for any service permission — SERVICE_ORDER or SERVICE_STORE_CONFIG at the tenant, at an organization or at any one store, or SERVICE_CONFIG, which is held at the tenant only — because whoever configures the job types reads them, and the service screens read them to work. A tenant-wide ADMIN grant counts as every permission. A caller holding none of them, a user with no role assignments included, is refused with a 403.\n\nRequired permissions: SERVICE_ORDER, SERVICE_STORE_CONFIG, SERVICE_CONFIG","parameters":[{"$ref":"#/components/parameters/serviceFormServiceTypeUidQuery"},{"$ref":"#/components/parameters/pageNumberQuery"},{"$ref":"#/components/parameters/pageSizeQuery"},{"$ref":"#/components/parameters/sortByQuery"},{"$ref":"#/components/parameters/sortDirectionQuery"}]}}}}
```


---

# 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://docs.flowretail.com/docs/developers/api-documentation/service/list-service-job-types.md?ask=<question>&goal=<user_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.
