Guides by flow
Search
/v1/search — plots, places, coordinates and jurisdictions in a single list.
Fuente del diagrama (mermaid)
flowchart TD
Q[query] --> L{¿≥ 2 caracteres?}
L -- no --> Z[lista vacía, sin red]
L -- sí --> C[Coordenadas pegadas]
L --> T[AOIs, carteras y siniestros del tenant]
L --> G[Lugares y jurisdicciones]
C & T & G --> R[Una lista, lo del tenant primero]
curl -sS "$SBOX/v1/search?q=Pergamino" -H "authorization: Bearer $TOKEN"
curl -sS "$SBOX/v1/search?q=-33.8921,%20-60.5736" -H "authorization: Bearer $TOKEN"
curl -sS "$SBOX/v1/cortex/geocode?q=Rojas" -H "authorization: Bearer $TOKEN"Pasted coordinates
Both readings are returned when both are valid. In Argentina −60,−33 and −33,−60 are both legitimate points: silently choosing one sends the user to stare at the sea.
What breaks
- Fewer than two characters does not fire. Every keystroke launching a search would return the entire portfolio and make the list flicker.
- A downed geocoder does not take the local results with it. The response
carries
degraded: trueand the tenant's own results still appear: your own data is what gets searched most, and degrading to zero turns an annoyance into an outage. You can exercise it with?geocoder=down. - Results respect the permission of their area. A claim does not appear for someone with only portfolio permission: it would be the same leak as the copilot, through another window.
- The query never enters the log. Length and digest are recorded. Someone pastes a client's tax ID on day one, and if that lands in a log the PII left through the door nobody watches.