---
title: "Update Location"
method: PATCH
path: "/v2/locations/{locationID}"
tags: ["Routes", "Locations"]
---

# Update Location

`PATCH /v2/locations/{locationID}`

This request updates a Location.

**Body parameter descriptions**

name | String | Optional | The new name of the Location.
timezone | string | Optional | The timezone this location resides in. This accepts a standard tz database name, see here.
phone | string | Optional | The phone number associated with this location.
weeklyOperationHours | Int | Optional | The number of hours your Assets run at this location per week. This is used to help calculate MTBF.
address | string | Optional | The physical address of this location.
address2 | string | Optional | The physical address of this location.
geoLocation | geoJSON | Optional | The geoJSON Feature object that can be used to locate a Limble location on a Map., To remove geoLocation from a Limble Location pass an empty object ( {}).
currencyCode | string | Optional | The ISO code for the currency at this location. For example: "USD".
regionID | integer | Optional | Assign, reassign, or unassign this location's region. Use 0 to unassign.

## Response `200`

The operation completed successfully. The response body is empty.

## Other responses

- `400` — The request was malformed — either invalid JSON syntax or a validation failure (missing required field, wrong type, etc.).
- `401` — No `Authorization` header was provided on the request.
- `403` — The supplied credentials are invalid, the customer account is inactive, or the credentials do not have permission to perform this action.
- `404` — The referenced resource does not exist or is not visible to the authenticated customer.
- `409` — The request conflicts with the current state of the resource (e.g. a uniqueness constraint or a referenced parent that is in the wrong state).
- `429` — The per-minute or per-hour rate limit for this credential and method has been exhausted. Inspect the `X-RateLimit-*` headers to determine when to retry.
- `500` — An unhandled server-side error. The body message is generic (`System unavailable...`) when the underlying cause is a database fault; otherwise it reflects the raised error.

---

[API](https://skmtc.net/limblecmms/apis/limble-api-v2.md) · [All operations](https://skmtc.net/limblecmms/apis/limble-api-v2/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/limblecmms/limble-api-v2/versions/20801e23f7f2/schema)