Co-tenant
Look up geocoding, building footprint, and co-tenant mix for a US address.
Overview
/co-tenantUse this endpoint when you need property-level context for an address:
- Geocode (latitude and longitude)
- Building footprint when available
- County name
- Businesses (co-tenants) associated with the location
This does not classify a company into NAICS. For industry codes, use Classification (POST /marvin2).
Each successful call consumes one Marvin2 API quota unit. This endpoint does not return an X-Marvin2-Cache header.
For the complete field list, see the co-tenant API reference.
Example request
Send a JSON body with all four address fields. Partial addresses return HTTP 400.
POST /co-tenant
Response
A successful response returns HTTP 200. Fields vary by address match quality — not every location returns tenants or a structure polygon.
| Field | Meaning |
|---|---|
geocode | Matched coordinates (lat, lng) |
structure.structure_polygon | Building footprint when available |
tenants | Businesses at or near the address (location_name, categories, NAICS when present) |
county_name | County for the matched address |
timestamp | Response generation time (ISO 8601) |
traceId | Include in support requests when debugging |
Example response (abbreviated)
An empty tenants array usually means no co-tenant records were found for that address, not that the request failed.
Platform API alternative
If your account includes property insights on the Platform API, you can request co-tenant context as part of POST /v1/business/risk by including the propertyInsights category (when enabled for your organization).
Use POST /co-tenant when you only need address-level property data, or when building a dedicated property workflow.
Errors
| Status | Typical cause |
|---|---|
| 400 | Invalid JSON or missing required address fields |
| 401 | Missing or invalid API key |
| 403 | Quota exceeded or not authorized |
| 502 | Upstream property data provider error |
| 503 | Service configuration error — retry later |
| 504 | Timeout communicating with upstream property data |
Include traceId from the response body when contacting support.