List location types
const url = 'https://example.com/api/v1/location-types';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url https://example.com/api/v1/location-typesLists the location_type registry (the shape-definers a location is classified by), ordered alphabetically by label. Populates the type picker on the location form. Gated by location_type:read.
Responses
Section titled “ Responses ”OK
object
A URL to the JSON Schema for this object.
object
A URL to the JSON Schema for this object.
True when this shipped row carries changes of yours overriding it. Restore discards them
The location type’s uuid, the stable handle that survives a rename
The label template locations of this type get; empty falls back to the global rule for locations
The name an operator reads and types; renameable
How the platform NAMES locations of this type; absent means an operator names every one of them
object
True when the first of this stem in a parent carries no ordinal
The first two names this rule mints in one parent, produced by the same mint a create allocates from: the first shows whether the first of a stem carries a number, the second shows the shape every later one takes. Read these rather than rebuilding the shape, which is what keeps one definition of a generated name
The generated name’s prefix; empty makes the type positional
True for a row this release ships. A shipped row is never written by an operator: an edit forks it
Example
{ "$schema": "/api/v1/schemas/ListLocationTypesOutputBody.json", "location_types": [ { "$schema": "/api/v1/schemas/LocationTypeBody.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"}