Skip to main content
GET
/
v1
/
signals
/
geo
/
location
/
{geo_id}
Get active signals for a geo ID
curl --request GET \
  --url https://api.homelogs.io/v1/signals/geo/location/{geo_id} \
  --header 'X-API-Key: <api-key>'
{
  "geo_id": "<string>",
  "geo_type": "property",
  "state": "<string>",
  "count": 1,
  "signals": [
    {
      "signal_key": "<string>",
      "value": {},
      "score": 123,
      "confidence": 123,
      "decision": "<string>",
      "reasons": [
        "<string>"
      ],
      "computed_at": "2023-11-07T05:31:56Z"
    }
  ],
  "missing_signal_keys": [
    "<string>"
  ]
}
Returns active geo-scoped signal rows for one geo_id. Use this for a location-level read of hotspot or velocity-style signals that are already computed for that geography. For narrative examples and interpretation guidance, see Signals & Methodology.

​
Required input

  • geo_id (path, required)

​
Optional input

  • signal_keys (query, CSV list)

​
Example request

curl -sS "$API_BASE_URL/v1/signals/geo/location/geo_county_6973f63e37a900040c0d?signal_keys=roofing_activity_hotspot,hvac_activity_hotspot" \
  -H "x-api-key: $HOMELOGS_API_KEY"

​
Response shape

  • geo_id, geo_type, state
  • count
  • signals[] with signal_key, value, score, confidence, decision, reasons, computed_at
  • missing_signal_keys[]

Authorizations

​
X-API-Key
string
header
required

Path Parameters

​
geo_id
string
required
Example:

"geo_city_0200d4df17d3b8cd84c6"

Query Parameters

​
signal_keys
string

Optional CSV list of signal keys.

Example:

"roofing_activity_hotspot,hvac_activity_hotspot"

Response

Signal rows and missing key diagnostics.

​
geo_id
string
required
​
geo_type
enum<string> | null
required
Available options:
property,
jurisdiction,
city,
zip,
county,
state,
null
​
state
string
required
​
count
integer
required
Required range: x >= 0
​
signals
object[]
required
​
missing_signal_keys
string[]
required