> 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/record-service-order-terms-acceptance.md).

# Record service-order terms acceptance

Record that the customer accepted the terms and conditions on a service order — signed at the counter on the store's device, with the drawn signature sent along and kept on the record, or accepted in the store without it, on the printed service confirmation or by telling staff, where no signature is kept. The record snapshots the terms exactly as the service order carries them at that moment, so it says what the customer was shown, and a TERMS\_ACCEPTED event is written on the timeline. The request is refused when the service order has no terms — there is nothing to accept — and refused while a standing acceptance exists on it — one acceptance is what is asked, and it has been given. After a void, a new acceptance may be recorded. An acceptance the customer gives themselves in the service portal is written by the portal and is not recorded here, which is why PORTAL\_LINK cannot be sent as the method. Supply acceptanceUid to make the call idempotent: a repeat with the same acceptanceUid returns the record already created, rather than the refusal a second acceptance would get. This is a write on the case, so it belongs to the store that owns the service order: at any other store it is refused with a 403, where the case can be read but not worked on.

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":{"ServiceTermsAcceptanceResponse":{"description":"Example response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceTermsAcceptanceResponseSchema"}}}}},"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-_]+"},"ServiceTermsAcceptanceCreateRequestSchema":{"title":"ServiceTermsAcceptanceCreateRequestSchema","description":"An acceptance of the terms and conditions on a service order, recorded by staff — signed at the counter on the store's device, or given in the store without it, on the printed service confirmation or by telling staff.\nThe record snapshots the terms exactly as the service order carries them at that moment, so it says what the customer was shown. The request is refused when the service order has no terms — termsText and termsUrl both empty — because there is nothing to accept, and refused while a standing acceptance exists on the service order — one acceptance is what is asked, and it has been given. After a void, a new acceptance may be recorded.\nSupply acceptanceUid to make the call idempotent: a repeat with the same acceptanceUid returns the record already created, rather than the refusal a second acceptance would get.","type":"object","required":["method"],"properties":{"acceptanceUid":{"$ref":"#/components/schemas/UID"},"method":{"description":"How the customer accepted, out of the ways staff record an acceptance.","allOf":[{"$ref":"#/components/schemas/ServiceTermsRecordedViaENUM"}]},"signature":{"type":"string","minLength":1,"maxLength":500000,"description":"The signature as the customer drew it on the device, a PNG image encoded in base64. It is kept on the acceptance itself, not as an asset. Required when the method is COUNTER_DEVICE — a counter acceptance without a drawn signature is refused, and an empty string is not a signature. Left out when the method is IN_STORE, where it is refused: an in-store acceptance keeps no signature, and a sheet the customer signed stays in the store's own filing or is uploaded as an ordinary document on the service order if the store wants it on record."}}},"ServiceTermsRecordedViaENUM":{"title":"ServiceTermsRecordedViaENUM","description":"How an acceptance of the terms and conditions was given, when staff record it because it did not come through the service portal.\nCOUNTER_DEVICE: the customer signed at the counter on the store's device, the signature drawn on the screen and kept on the acceptance. IN_STORE: the customer accepted in the store without the counter device — by signing the printed service confirmation or by telling staff they accept; staff record that it happened, and no signature is kept on the acceptance. A signed sheet, where there is one, stays in the store's own filing — or is uploaded as an ordinary document on the service order, if the store wants it on record.\nAn acceptance the customer gives themselves in the service portal is recorded as PORTAL_LINK, which the portal writes itself. That is why PORTAL_LINK is not one of these values: this is what staff may record, not the whole set of ways an acceptance can be given.","type":"string","enum":["COUNTER_DEVICE","IN_STORE"]}},"requestBodies":{"ServiceTermsAcceptanceCreateRequest":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceTermsAcceptanceCreateRequestSchema"}}}}}},"paths":{"/tenants/{tenantUid}/stores/{storeUid}/serviceorders/{serviceOrderUid}/termsacceptances":{"post":{"summary":"Record service-order terms acceptance","operationId":"post-serviceorders-termsacceptances","description":"Record that the customer accepted the terms and conditions on a service order — signed at the counter on the store's device, with the drawn signature sent along and kept on the record, or accepted in the store without it, on the printed service confirmation or by telling staff, where no signature is kept.\nThe record snapshots the terms exactly as the service order carries them at that moment, so it says what the customer was shown, and a TERMS_ACCEPTED event is written on the timeline. The request is refused when the service order has no terms — there is nothing to accept — and refused while a standing acceptance exists on it — one acceptance is what is asked, and it has been given. After a void, a new acceptance may be recorded.\nAn acceptance the customer gives themselves in the service portal is written by the portal and is not recorded here, which is why PORTAL_LINK cannot be sent as the method. Supply acceptanceUid to make the call idempotent: a repeat with the same acceptanceUid returns the record already created, rather than the refusal a second acceptance would get.\nThis is a write on the case, so it belongs to the store that owns the service order: at any other store it is refused with a 403, where the case can be read but not worked on.\n\nRequired permissions: SERVICE_ORDER","responses":{"201":{"$ref":"#/components/responses/ServiceTermsAcceptanceResponse"},"409":{"description":"Conflict. The service order has no terms, so there is nothing to accept; or an acceptance already stands on it, and one acceptance is what is asked. Nothing is written."}},"requestBody":{"$ref":"#/components/requestBodies/ServiceTermsAcceptanceCreateRequest"},"tags":["Service"]}}}}
```


---

# 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/record-service-order-terms-acceptance.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.
