> 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/open-a-counter-signing-session.md).

# Open a counter signing session

Open a session for signing the terms of a service order on a device at the counter, and get back the URL that device opens. This is how a customer signs on the counter device: staff never show them the link that follows their case, because that link reaches the whole portal and stays alive long after they have walked out. The session shows the service order's terms — the tenant's text with the type's addition, exactly as the service order carries them — and captures the signature, and reaches nothing else on the service order. It is refused when the service order has no terms, and refused while a standing acceptance exists on it: there is nothing left to sign. A session lives a few minutes, not hours: the window is fixed and the tenant does not configure it. It also stops working the moment the terms are accepted, when the service order's customer is changed, and when a new session is created for the same service order — creating one replaces the last, so the URL on a device someone forgot to close is already dead. Accepting through it records the acceptance with method COUNTER\_DEVICE, with the drawn signature on the record, and writes a TERMS\_ACCEPTED event on the timeline, exactly as an acceptance recorded by staff does. 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":{"ServiceOrderSigningSessionResponse":{"description":"Example response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceOrderSigningSessionResponseSchema"}}}}},"schemas":{"ServiceOrderSigningSessionResponseSchema":{"title":"ServiceOrderSigningSessionResponseSchema","description":"A short-lived session for signing the terms of a service order on a device handed across the counter. It is what staff open when the customer is standing there, in place of showing them the link that follows their case.\nThe session reaches nothing but the terms: it shows the text and captures the signature, and it cannot be turned into the customer's service portal, because it is not that link and never carries it.\nA session lives a few minutes — long enough to read and sign at the counter, and no longer. The window is fixed and the tenant does not configure it. Creating a session for a service order replaces the last one made for it, so the URL on a device someone forgot to close is already dead.","type":"object","required":["signingUrl","expiresAt"],"properties":{"signingUrl":{"type":"string","description":"The full URL the counter device opens. It carries the session's own single-use token, which belongs to this session alone and to no other surface — hand the device over on this page and nothing else on the service order is within reach."},"expiresAt":{"type":"string","format":"date-time","description":"When the session stops working of its own accord — a few minutes out, which is what the session is for: long enough for a customer to read and sign at the counter, not long enough to be useful once the device has been put down."}}}}},"paths":{"/tenants/{tenantUid}/stores/{storeUid}/serviceorders/{serviceOrderUid}/signingsession":{"post":{"summary":"Open a counter signing session","operationId":"post-serviceorders-signingsession","description":"Open a session for signing the terms of a service order on a device at the counter, and get back the URL that device opens. This is how a customer signs on the counter device: staff never show them the link that follows their case, because that link reaches the whole portal and stays alive long after they have walked out.\nThe session shows the service order's terms — the tenant's text with the type's addition, exactly as the service order carries them — and captures the signature, and reaches nothing else on the service order. It is refused when the service order has no terms, and refused while a standing acceptance exists on it: there is nothing left to sign.\nA session lives a few minutes, not hours: the window is fixed and the tenant does not configure it. It also stops working the moment the terms are accepted, when the service order's customer is changed, and when a new session is created for the same service order — creating one replaces the last, so the URL on a device someone forgot to close is already dead.\nAccepting through it records the acceptance with method COUNTER_DEVICE, with the drawn signature on the record, and writes a TERMS_ACCEPTED event on the timeline, exactly as an acceptance recorded by staff does.\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/ServiceOrderSigningSessionResponse"},"409":{"description":"Conflict. The service order has no terms, or an acceptance already stands on it: there is nothing left to sign, and no session is opened."}},"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/open-a-counter-signing-session.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.
