Endpoint
POST /api/v1/location/ (identical behavior).
Auth: None (public)
Purpose
Resolve alocation_hash you already hold to the street address it belongs to — for example, to display the install address for a session or hand-off. The lookup direction is hash → address, not address → hash.
Request body
Provide at least one of the two fields (location_hash is preferred; if both are sent, location_hash wins):
Sending neither fails validation with
"Provide location_hash or location_identifier" (422).
Response — 200 OK
The location’s address row (the joinedaddresses record) plus three
fields that identify the location itself (added 2026-09-15, additive):
Errors
Related
POST /partner/location/details exists on the same router and returns the full location record (switch, port, unit), but it requires a dashboard JWT — it is an operator endpoint, not callable with partner credentials.