Skip to main content

Overview

The Locations API manages physical addresses where business entities operate, including registered offices, operating addresses, warehouses, branches, and points of sale. Locations are used for registration threshold determination, compliance tracking, and employee management.

Core endpoints

List locations

Get all locations for a business entity.
Path parameters Response
createdAt, updatedAt and archivedAt are Unix timestamps in milliseconds. endDate is included once the location has one.

Get location

Retrieve a single location by ID.
Path parameters Response

Create location

Add a new location to a business entity.
Path parameters Request body
An entity can have only one REGISTERED_OFFICE location and one MAILING_ADDRESS location. Creating a second one returns 400 Bad Request. Response Returns 201 Created.

Update location

Update an existing location.
Path parameters Request body Takes the same fields as Create location, all optional. When you send address, include its required fields.
An endDate before the location’s start date is rejected with 400 Bad Request. Response Returns 200 OK with no body.

Delete location

Remove a location from a business entity.
Path parameters Response Returns 204 No Content on success.

Location types

A single location can have multiple types (e.g., ["PRINCIPAL_PLACE_OF_BUSINESS", "REGISTERED_OFFICE"]):

Address fields

The address object takes these fields:

Employee tracking

Track employee count at each location for:
  • Payroll tax threshold determination
  • Workers’ compensation requirements
  • Local tax obligations
  • Headcount reporting
Update employeeCount as staff levels change.

Registration threshold determination

Use startDate to track when physical presence began in a jurisdiction. This is critical for:
  • Indirect tax registration thresholds
  • Income tax registration thresholds
  • Payroll tax obligations
  • Registration requirements

Location sources

Locations you create through this API are recorded as entered in CommendaOS. The source of a location is not returned in location responses.

Time periods

Track location validity with startDate and endDate:
  • startDate: When the location became active (optional)
  • endDate: When the location was closed (optional, absent for active locations)
This enables historical tracking of where entities operated over time.