> 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-the-expected-turnaround-of-every-service-type-at-a-store.md).

# List the expected turnaround of every service type at a store

List the expected turnaround of every service type at this store in one read: one item per service type of the tenant that is not deprecated, each resolved exactly as get-serviceorders-types-turnaround answers it for that type — the same effective figure, resolution and readyAtEstimate. Each item carries its serviceTypeUid, and the answer is an array of items, not a map keyed by service type. A deprecated service type is left out, although put-serviceorders-types-turnaround still accepts an override on one. The list is not paged: the tenant's list of service types bounds it. It is ordered by service type name, with the uid as the tiebreaker. It is what a screen listing every service type's turnaround at a store reads, instead of one get-serviceorders-types-turnaround call per type. A tenant with no service type that is not deprecated answers an empty list. Reading them asks for any service permission — SERVICE\_ORDER or SERVICE\_STORE\_CONFIG held at this store, at its organization or at the tenant, or SERVICE\_CONFIG, which is held at the tenant only — because whoever sets the store's turnarounds reads them. A tenant-wide ADMIN grant counts as every permission. A caller holding none of them at this store, a user with no role assignments included, is refused with a 403, and a storeUid naming no store of the tenant with a 400.

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":{"ServiceTypeTurnaroundListResponse":{"description":"Example response","content":{"application/json":{"schema":{"type":"object","properties":{"items":{"type":"array","items":{"$ref":"#/components/schemas/ServiceTypeTurnaroundResponseSchema"}}},"required":["items"]}}}}},"schemas":{"ServiceTypeTurnaroundResponseSchema":{"title":"ServiceTypeTurnaroundResponseSchema","description":"The expected turnaround that applies to one service type at one store, together with the level it was found at. A figure set for the store wins over the tenant's figure on the service type, so this is what intake reads rather than either one on its own.\nestimatedBusinessDays is the effective figure: the store's own where the store has one, and the service type's otherwise. readyAtEstimate is the date core computes from it for a service order registered now, so the client never does the business-day arithmetic itself. Both are null when neither level carries a figure, and nothing is prefilled. readyAtEstimate is also null, and nothing is prefilled, when no day of the week can be one of the store's working days (its openDays hold only Saturday and Sunday and serviceCountWeekendsAsWorkingDays is false).","type":"object","required":["tenantUid","storeUid","serviceTypeUid","estimatedBusinessDays","readyAtEstimate","resolution"],"properties":{"tenantUid":{"$ref":"#/components/schemas/UID"},"storeUid":{"$ref":"#/components/schemas/UID"},"serviceTypeUid":{"$ref":"#/components/schemas/UID"},"estimatedBusinessDays":{"type":"integer","nullable":true,"description":"The expected turnaround that applies here, in business days. null when neither the store nor the service type carries a figure. The date it yields is readyAtEstimate on this response: the client reads the prefilled date off the response rather than computing it, and staff adjust that date case by case."},"readyAtEstimate":{"type":"string","format":"date-time","nullable":true,"description":"The date intake prefills the service order's readyAtEstimate with: the day of this request in the tenant's timezone plus estimatedBusinessDays of the store's working days (serviceCountWeekendsAsWorkingDays), at 23:59:59 on that day in the tenant's timezone, which reads as the end of the day with no time picked, as readyAtEstimate on the service order response states. Counting starts on the day of the request, or on the next working day when the request falls on a non-working day, so 0 business days answers that starting day. Core does the arithmetic; the client never counts days itself.\nnull when estimatedBusinessDays is null, or when no day of the week can be one of the store's working days (its openDays hold only Saturday and Sunday and serviceCountWeekendsAsWorkingDays is false), and nothing is prefilled. The client shows the day and time on the intake form and sends the day and time the staff kept, adjusted or cleared as readyAtEstimate on the service order create; the create never prefills a date on its own."},"resolution":{"description":"The level the figure was found at. STORE when the store has an override of its own, TENANT when it falls back to the service type's figure — including when that figure is itself null.","allOf":[{"$ref":"#/components/schemas/ServiceTurnaroundResolutionENUM"}]}}},"UID":{"title":"UID","type":"string","pattern":"^[A-Za-z0-9-_]+"},"ServiceTurnaroundResolutionENUM":{"title":"ServiceTurnaroundResolutionENUM","description":"The level the expected turnaround was found at.\nSTORE: the store has an override of its own for this service type — a store figure always wins. TENANT: the store has no override, so the service type's own figure applies, which may itself be none.","enum":["STORE","TENANT"],"type":"string"}}},"paths":{"/tenants/{tenantUid}/stores/{storeUid}/serviceorders/types/turnarounds":{"get":{"summary":"List the expected turnaround of every service type at a store","tags":["Service"],"responses":{"200":{"$ref":"#/components/responses/ServiceTypeTurnaroundListResponse"}},"operationId":"get-serviceorders-types-turnarounds","description":"List the expected turnaround of every service type at this store in one read: one item per service type of the tenant that is not deprecated, each resolved exactly as get-serviceorders-types-turnaround answers it for that type — the same effective figure, resolution and readyAtEstimate. Each item carries its serviceTypeUid, and the answer is an array of items, not a map keyed by service type.\nA deprecated service type is left out, although put-serviceorders-types-turnaround still accepts an override on one.\nThe list is not paged: the tenant's list of service types bounds it. It is ordered by service type name, with the uid as the tiebreaker.\nIt is what a screen listing every service type's turnaround at a store reads, instead of one get-serviceorders-types-turnaround call per type.\nA tenant with no service type that is not deprecated answers an empty list.\nReading them asks for any service permission — SERVICE_ORDER or SERVICE_STORE_CONFIG held at this store, at its organization or at the tenant, or SERVICE_CONFIG, which is held at the tenant only — because whoever sets the store's turnarounds reads them. A tenant-wide ADMIN grant counts as every permission. A caller holding none of them at this store, a user with no role assignments included, is refused with a 403, and a storeUid naming no store of the tenant with a 400.\n\nRequired permissions: SERVICE_ORDER, SERVICE_STORE_CONFIG, SERVICE_CONFIG"}}}}
```


---

# 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-the-expected-turnaround-of-every-service-type-at-a-store.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.
