> 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/update-service-hours-entry.md).

# Update service hours entry

Deprecated. Hours registration is superseded: all work on a service order is product lines. Register time-billed work as an ordinary service order item for an hour product, where the quantity is the number of hours. Like every quantity in the platform, the item quantity is in hundredths (100 = 1 unit), so fractional time is an ordinary quantity: 2.5 hours = 250. Use `/tenants/{tenantUid}/stores/{storeUid}/serviceorders/{serviceOrderUid}/items` instead. This endpoint will be removed after the announced deprecation window; see the deprecation log for the date.

Update a service hours entry. 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":{"ServiceHoursResponse":{"description":"Example response","content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceHoursResponseSchema"}}}}},"schemas":{"ServiceHoursResponseSchema":{"deprecated":true,"description":"Deprecated. Hours registration is superseded: all work on a service order is product lines. Read the work on a service order from its service order items instead — time-billed work is an item for an hour product. This schema will be removed after the announced deprecation window; see the deprecation log for the date.","title":"ServiceHoursResponseSchema","type":"object","required":["serviceHoursUid","serviceOrderUid","tenantUserUid","note","serviceDate","usedMinutes","billedMinutes","hourPrice","totalPrice","tenantUserDisplayName","createdAt","createdBy","lastModifiedAt","lastModifiedBy","hourlyRateUid","salesOrderUid"],"properties":{"serviceHoursUid":{"$ref":"#/components/schemas/UID"},"serviceOrderUid":{"$ref":"#/components/schemas/UID"},"tenantUserUid":{"$ref":"#/components/schemas/UID"},"note":{"type":"string"},"serviceDate":{"type":"string","format":"date-time"},"usedMinutes":{"type":"integer"},"billedMinutes":{"type":"integer"},"hourPrice":{"type":"integer"},"totalPrice":{"type":"integer"},"tenantUserDisplayName":{"type":"string"},"createdAt":{"type":"string","format":"date-time"},"createdBy":{"type":"string"},"lastModifiedAt":{"type":"string","format":"date-time"},"lastModifiedBy":{"type":"string"},"hourlyRateUid":{"$ref":"#/components/schemas/UID"},"salesOrderUid":{"$ref":"#/components/schemas/UID"}}},"UID":{"title":"UID","type":"string","pattern":"^[A-Za-z0-9-_]+"},"ServiceHoursUpdateRequestSchema":{"deprecated":true,"description":"Deprecated. Register time-billed work as an ordinary service order item for an hour product instead, where the quantity is the number of hours. Like every quantity in the platform, the item quantity is in hundredths (100 = 1 unit), so fractional time is an ordinary quantity: 2.5 hours = 250. This schema will be removed after the announced deprecation window; see the deprecation log for the date.","title":"ServiceHoursUpdateRequestSchema","type":"object","properties":{"serviceDate":{"type":"string","format":"date-time"},"usedMinutes":{"type":"integer"},"note":{"type":"string"},"billedMinutes":{"type":"integer"},"hourlyRateUid":{"$ref":"#/components/schemas/OptionalUID"}}},"OptionalUID":{"title":"OptionalUID","type":"string","pattern":"^[A-Za-z0-9-_]*"}},"requestBodies":{"ServiceHoursUpdateRequest":{"content":{"application/json":{"schema":{"$ref":"#/components/schemas/ServiceHoursUpdateRequestSchema"}}}}}},"paths":{"/tenants/{tenantUid}/stores/{storeUid}/serviceorders/{serviceOrderUid}/hours/{serviceHoursUid}":{"put":{"summary":"Update service hours entry","operationId":"put-serviceorders-hours","description":"Deprecated. Hours registration is superseded: all work on a service order is product lines. Register time-billed work as an ordinary service order item for an hour product, where the quantity is the number of hours. Like every quantity in the platform, the item quantity is in hundredths (100 = 1 unit), so fractional time is an ordinary quantity: 2.5 hours = 250. Use `/tenants/{tenantUid}/stores/{storeUid}/serviceorders/{serviceOrderUid}/items` instead. This endpoint will be removed after the announced deprecation window; see the deprecation log for the date.\n\nUpdate a service hours entry.\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","deprecated":true,"responses":{"200":{"$ref":"#/components/responses/ServiceHoursResponse"}},"tags":["Service"],"requestBody":{"$ref":"#/components/requestBodies/ServiceHoursUpdateRequest"}}}}}
```


---

# 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/update-service-hours-entry.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.