> 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-order-terms-acceptances.md).

# List service-order terms acceptances

List the acceptances of the terms and conditions recorded on a service order — when the customer agreed, how, and to what wording. A service order asks for one acceptance and carries at most one that stands, so the list is the history: the one that stands, if any, and the ones voided before it. Each acceptance carries the terms exactly as the service order showed them at that moment and the signature drawn at the counter where there is one. Changing the tenant's or the type's terms afterwards never rewrites these records, so the list always answers what was agreed to at the time rather than what the terms say today. Acceptances that have been voided are listed too, carrying the reason they were voided. They are kept as the business fact they are, and they satisfy nothing. Read at any store of the tenant: the store in the path is where the permission is judged, and nothing more; the service order record carries the whole reach rule.

Required permissions: SERVICE\_ORDER

```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":{"ServiceTermsAcceptanceListResponse":{"description":"Example response","content":{"application/json":{"schema":{"type":"object","properties":{"items":{"type":"array","items":{"$ref":"#/components/schemas/ServiceTermsAcceptanceResponseSchema"}},"paging":{"$ref":"#/components/schemas/Paging"}},"required":["items","paging"]}}}}},"schemas":{"ServiceTermsAcceptanceResponseSchema":{"title":"ServiceTermsAcceptanceResponseSchema","description":"A record that the customer accepted the terms and conditions on a service order. It is a business fact. One acceptance is what a service order asks for, and one standing acceptance is what it carries.\nThe evidence on it never changes once recorded: when the customer accepted (acceptedAt), how (method), the terms exactly as they read when they accepted (termsText, termsUrl) and the signature drawn on the counter device where there is one. The only later write the record takes is being voided, which sets voidReason and nothing else. termsText and termsUrl are the wording the acceptance answered; a later change of the tenant's terms, of the type's additional terms or of the service order's service type never touches them, so what was agreed to can always be established.\nmethod says how the acceptance was given. Every way carries the same weight — the difference is only where the customer was standing and how they gave it.\nAn acceptance that has been voided is still here, and still says what it said: the evidence stays as recorded, voidReason carries the reason, and an acceptance that has been voided satisfies nothing on the service order.","type":"object","required":["acceptanceUid","serviceOrderUid","method","signature","termsText","termsUrl","acceptedAt","voidReason"],"properties":{"acceptanceUid":{"$ref":"#/components/schemas/UID"},"serviceOrderUid":{"$ref":"#/components/schemas/UID"},"method":{"type":"string","description":"How the terms were accepted.\nPORTAL_LINK: the customer accepted in the service portal, through the link in the message they were sent. COUNTER_DEVICE: the customer signed at the counter on the store's device, and the drawn signature is on the record. IN_STORE: the customer accepted in the store — on the printed service confirmation or by telling staff — and staff recorded that it happened.","enum":["PORTAL_LINK","COUNTER_DEVICE","IN_STORE"]},"signature":{"type":"string","description":"The signature as the customer drew it on the counter device, a PNG image encoded in base64, kept on the acceptance itself. Set on every acceptance whose method is COUNTER_DEVICE. An empty string on the other two: an acceptance given in the service portal or in the store draws nothing."},"termsText":{"type":"string","description":"The terms the customer accepted, in the terms format that termsText in the service settings describes, exactly as the service order carried them at that moment — the tenant's terms followed by the additional terms of the service order's service type. Compare it with the service order's current termsText to see whether the wording accepted is still the one the service order carries."},"termsUrl":{"type":"string","description":"The URL of the tenant's published terms as the service order carried it when the customer accepted. An empty string when there was none."},"acceptedAt":{"type":"string","format":"date-time","description":"When the customer accepted. Who recorded it — the staff member in the store, or the portal itself — is the attribution of the TERMS_ACCEPTED event on the timeline; the customer is the one accepting on every channel."},"voidReason":{"type":"string","description":"The reason the acceptance was voided, as the user who voided it wrote it. An empty string on an acceptance that stands. Who voided it and when are on the TERMS_VOIDED event written on the timeline."}}},"UID":{"title":"UID","type":"string","pattern":"^[A-Za-z0-9-_]+"},"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":{"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}/stores/{storeUid}/serviceorders/{serviceOrderUid}/termsacceptances":{"get":{"summary":"List service-order terms acceptances","tags":["Service"],"responses":{"200":{"$ref":"#/components/responses/ServiceTermsAcceptanceListResponse"}},"operationId":"get-serviceorders-termsacceptances","description":"List the acceptances of the terms and conditions recorded on a service order — when the customer agreed, how, and to what wording. A service order asks for one acceptance and carries at most one that stands, so the list is the history: the one that stands, if any, and the ones voided before it.\nEach acceptance carries the terms exactly as the service order showed them at that moment and the signature drawn at the counter where there is one. Changing the tenant's or the type's terms afterwards never rewrites these records, so the list always answers what was agreed to at the time rather than what the terms say today.\nAcceptances that have been voided are listed too, carrying the reason they were voided. They are kept as the business fact they are, and they satisfy nothing.\nRead at any store of the tenant: the store in the path is where the permission is judged, and nothing more; the service order record carries the whole reach rule.\n\nRequired permissions: SERVICE_ORDER","parameters":[{"$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-order-terms-acceptances.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.
