> 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/get-service-insurance-company.md).

# Get service insurance company

Get an insurance company entry by ID, with the linked customer's uid and name as they read now. Reading it 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 insurance companies 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":{"InsuranceCompanyResponse":{"description":"Example response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/InsuranceCompanyResponseSchema"}}}}},"schemas":{"InsuranceCompanyResponseSchema":{"title":"InsuranceCompanyResponseSchema","description":"An insurance company entry: one of the insurers the tenant's service orders name, linked to the customer record that stands for it. The tenant's entries are the intake wizard's insurer picker — picking one puts its customerUid on the service order as insuranceCompanyCustomerUid, so no service order references the entry itself and it is deletable at any time.\nThe entry goes with its customer record: deleting the record deletes the entry, and merging the record into another customer moves the entry to that customer. customerName is the linked customer's display name as it reads now.\nA deprecated entry stays in the list but is not offered in the picker.","type":"object","required":["insuranceCompanyUid","tenantUid","name","customerUid","customerName","deprecated","createdAt","createdBy","lastModifiedAt","lastModifiedBy"],"properties":{"insuranceCompanyUid":{"$ref":"#/components/schemas/UID"},"tenantUid":{"$ref":"#/components/schemas/UID"},"name":{"type":"string","description":"What the insurer is called, as it is shown in the picker. Unique within the tenant."},"customerUid":{"description":"The customer record that stands for the insurer. Linked by this entry alone.","type":"string","pattern":"^[A-Za-z0-9-_]+"},"customerName":{"type":"string","description":"The linked customer's display name as it reads now."},"deprecated":{"type":"boolean","description":"A deprecated entry stays in the list but is not offered in the picker."},"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-_]+"}}},"paths":{"/tenants/{tenantUid}/serviceorders/insurancecompanies/{insuranceCompanyUid}":{"get":{"summary":"Get service insurance company","tags":["Service"],"responses":{"200":{"$ref":"#/components/responses/InsuranceCompanyResponse"}},"operationId":"get-serviceorders-insurancecompanies-id","description":"Get an insurance company entry by ID, with the linked customer's uid and name as they read now.\nReading it 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 insurance companies 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"}}}}
```


---

# 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/get-service-insurance-company.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.
