TerraCore API (Technical)

RapidAPI Host	`terracore-us-neighborhood-demographics-api.p.rapidapi.com`
Content-Type	`application/json`
Auth Header	`x-rapidapi-key: <your_rapidapi_key>`
Full Docs	`https://airelit.com/terracore/docs/`

Note: When consuming TerraCore through RapidAPI, use your RapidAPI key and the RapidAPI host shown above. Endpoint paths, request bodies, and response formats are identical to the TerraCore core API. RapidAPI connection details may change — always refer to the RapidAPI dashboard for the latest host and key requirements.

Endpoints (POST)

Coordinates	`/v1/terracore/coordinates`
ZIP Code	`/v1/terracore/zipcode`
GEOID	`/v1/terracore/geoid`
Address	`/v1/terracore/address`

Example Request (RapidAPI)

curl --request POST \
  --url https://terracore-us-neighborhood-demographics-api.p.rapidapi.com/v1/terracore/coordinates \
  --header 'Content-Type: application/json' \
  --header 'x-rapidapi-host: terracore-us-neighborhood-demographics-api.p.rapidapi.com' \
  --header 'x-rapidapi-key: <your_rapidapi_key>' \
  --data '{"lat":40.7128,"lon":-74.006,"fields":["summary","walkability","transit_access"]}'

Request Body (by endpoint) 1) Coordinates

{
  "lat": 32.7767,
  "lon": -96.7970,
  "fields": ["summary","income","indices"]
}

2) ZIP Code

{
  "zipcode": "84015",
  "fields": ["summary","demographics","income","zip_environment_scores","zip_indices"]
}

3) GEOID

{
  "geoid": "481130166001",
  "fields": ["all"]
}

4) Address

{
  "address": "1735 Millhouse Run NE, Marietta, GA",
  "fields": ["summary","walkability"]
}

fields Parameter

Type	`array[string]`
Optional	`true` (if omitted, `summary` is returned by default)
Special	`["all"]` returns all available field groups for your plan/tier

Available Field Groups (for fields[])

Field availability varies by subscription tier. ZIP-exclusive groups are only returned by the /zipcode endpoint.

Core Metrics

Group	Description	Available Tier
`summary`	Core identifiers + headline stats	Basic (Free)
`demographics`	Age / household structure	Basic (Free)
`race`	Race / ethnicity composition	Basic (Free)
`income`	Income + poverty metrics	Basic (Free)
`education`	Educational attainment	Basic (Free)
`employment`	Employment / labor force	Basic (Free)
`housing`	Housing occupancy / tenure	Basic (Free)
`jurisdictions`	Political and school jurisdiction	Basic (Free)
`commute`	Commute / transportation	Pro
`internet`	Internet / broadband indicators	Pro
`insurance`	Insurance coverage	Pro
`raw_counts`	Underlying raw count values. Not available for ZIP lookups.	Pro

Composite Indices

Group	Description	Available Tier
`indices`	Composite / percentile-ranked indices	Pro

Location Intelligence Metrics — Block Group queries only (coordinates, GEOID, address)

Group	Description	Available Tier
`walkability`	Amenity counts / proximity signals	Pro
`grocery_access`	Grocery proximity metrics	Pro
`healthcare_access`	Healthcare proximity metrics	Pro
`transit_access`	Transit proximity metrics	Pro
`retail`	Retail proximity / density signals	Pro
`school_access`	School proximity metrics	Pro
`recreation`	Parks / recreation proximity metrics	Pro
`community_access`	Community services proximity metrics	Pro
`enrichment_meta`	Metadata (vintage / processing)	Pro

ZIP-Exclusive Fields — /zipcode endpoint only

Group	Description	Available Tier
`zip_environment_scores`	Population-weighted averages of environment scores across contributing block groups	Pro
`zip_poi_distances`	Population-weighted average distances to key amenities (grocery, hospital, park, transit)	Pro
`zip_amenity_counts`	Direct counts of amenities within the ZIP boundary (OpenStreetMap-derived)	Pro
`zip_amenity_ratios`	Population-normalized amenity density metrics derived from ZIP amenity counts	Pro
`zip_indices`	ZIP-level composite indices for neighborhood livability and retail opportunity (nationally percentile-ranked)	Pro

Group	Description	Available Tier
`all`	All available groups for your subscribed tier	Tier-Based

Response Fields

Total Fields Available	More than 200 fields across all field groups
Format	JSON object grouped by requested field blocks
Notes	Not all blocks may be present depending on `fields` and plan/tier

For the complete field list with descriptions, data types, and example values, see the full TerraCore API reference: https://airelit.com/terracore/docs/

Error Codes

`INVALID_PARAMS`	400	Input validation failed. Check that `lat`/`lon` are valid numbers, `zipcode` is exactly 5 digits, and `geoid` is exactly 12 digits.
`INVALID_JSON`	400	Request body is not valid JSON. Ensure `Content-Type: application/json` is set and the body is well-formed.
`UNAUTHORIZED`	401	Missing or invalid API key.
`NOT_FOUND`	404	No data found for the given input. Coordinates may be in a water area, the ZIP may not exist in our dataset, or the GEOID may be invalid.
`OUT_OF_BOUNDS`	422	Coordinates fall outside supported US coverage (50 states, DC, Puerto Rico).
`TIER_REQUIRED`	403	Requested field group not available for current plan/tier. Upgrade your plan or remove the restricted groups from your `fields` array.
`QUOTA_EXCEEDED`	429	Rate limit or request quota exceeded. Quota may be enforced by the Airelit platform or by the RapidAPI gateway.
`INTERNAL_ERROR`	500	Unexpected server error. Retry the request. If the issue persists, contact support with the returned `request_id`.

Sample Data & Integration Resources

To view full JSON responses, CSV exports, and implementation logic, visit our official examples repository. Note that while the core data structures are identical, the GitHub examples use direct host headers; for RapidAPI, always use the x-rapidapi-host and x-rapidapi-key shown above.

Data Samples	`https://github.com/AireLit/terracore-examples/tree/main/sample-data`
Code Examples	`https://github.com/AireLit/terracore-examples`