---
title: "New Location"
method: POST
path: "/v2/locations"
tags: ["Routes", "Locations"]
---

# New Location

`POST /v2/locations`

This request creates a new Location.

**Body parameter descriptions**

name | String | Required | The new name of the Location.
timezone | string | Required | The timezone this location resides in. This accepts a standard tz database name, see here.
phone | string | Required | The phone number associated with this location.
weeklyOperationHours | Int | Optional | The hours per week this location operates.
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.
extraNotificationsEmail | string | Optional | Include an email address to receive notifications for the location.
currencyCode | string | Optional | The ISO code for the currency at this location. For example: "USD".
regionID | integer | Optional | The region to assign this location to. Omit to leave unassigned. Use 0 for unassigned.

## Response `201`

New Location

- object
  - `locationID` string, utc-millisec

## 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.
- `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/revisions/eceb9442ed4d/schema)