Regenerate a location's name
const url = 'https://example.com/api/v1/locations/example:resetName';const options = {method: 'POST'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://example.com/api/v1/locations/example:resetNameHands the pen back to the platform, the same verb components and systems carry: the name is re-minted from the location_type’s name rule and the lowest free ordinal in this placement, and name_generated goes back to true. A location_type carrying no name rule refuses (422), which is every type a shipped fleet has: only a positional kind of place, one whose number is an arbitrary disambiguator rather than a designation read off the signage (a parking deck, a rack row), has a name the platform can generate, and an operator declares such a type themselves. Gated by location:rename, the same token :rename uses.
Parameters
Section titled “ Parameters ”Path Parameters
Section titled “Path Parameters ”The location’s name, or a dotted address (e.g. boi.17c.415a)
The location’s name, or a dotted address (e.g. boi.17c.415a)
Responses
Section titled “ Responses ”OK
object
A URL to the JSON Schema for this object.
The scope-aware actions the caller may perform on this row (create a child, update, delete); a UI hint, the server still enforces.
The resolved effective tags (key -> winning value) that cascade onto this location (platform and its location tree); for the Tags column.
object
Whether the platform rendered this label from a label rule rather than an operator typing it. Read-only: write label to claim it, write an empty label to hand it back.
The location_type name
The location_type’s uuid, the stable form of location_type
Whether the platform picked this name (from the location_type’s name rule) rather than an operator typing it.
The parent location’s name, for display; absent for a site root
The parent location’s id, the canonical handle
The dotted address (e.g. boi.17c.415a); no accessor, since a location’s own address IS its location-tree ancestor chain. Set on a GET or LIST response; empty on a create/update/move/rename response (refetch the row to see it).
Path split on ’.’.
Two display-only compact forms of path, dash and bare. Neither is accepted back by the resolver: stripping/compacting is lossy.
object
The dash render’s segments concatenated with no separator, with the final stem-ordinal segment compacted to
The path’s non-accessor segments joined with ’-’ (e.g. boi-17c-216b-display-1). Display only; not accepted by the resolver.
Example
{ "$schema": "/api/v1/schemas/LocationBody.json"}default
Section titled “default ”Error
object
A URL to the JSON Schema for this object.
A human-readable explanation specific to this occurrence of the problem.
Optional list of individual error details
object
Where the error occurred, e.g. ‘body.items[3].tags’ or ‘path.thing-id’
Error message text
The value at the given location
A URI reference that identifies the specific occurrence of the problem.
HTTP status code
A short, human-readable summary of the problem type. This value should not change between occurrences of the error.
A URI reference to human-readable documentation for the error.
Example
{ "$schema": "/api/v1/schemas/ErrorModel.json", "detail": "Property foo is required but is missing.", "instance": "https://example.com/error-log/abc123", "status": 400, "title": "Bad Request", "type": "about:blank"}