---
title: "Ownership"
description: "Resolve vehicle owners, contact details, and address residents from CarsXE's identity graph — by VIN, name and address, address alone, or ZIP code. Enterprise only."
canonical_url: "https://docs.carsxe.com/docs/products/ownership"
markdown_url: "https://docs.carsxe.com/docs/products/ownership.md"
last_updated: "1980-01-01"
---

# Ownership
URL: /docs/products/ownership
LLM index: /llms.txt
Description: Resolve vehicle owners, contact details, and address residents from CarsXE's identity graph — by VIN, name and address, address alone, or ZIP code. Enterprise only.

<Note variant="warning">
  The Ownership API is available on **Enterprise plans only**. If you're
  interested in access, [contact us](https://carsxe.com/contact) and we'll
  walk you through your options.
</Note>

Deep dive into Ownership — four lookup types that resolve people and contact details from CarsXE's identity graph. For the interactive playground, see the [API Reference](/api-reference/ownership/ownership-by-vin).

The Ownership API answers one core question from four different starting points: **who is connected to this vehicle or place?** You always have something to start from — a VIN, a name and address, just an address, or a ZIP code — and the API resolves the rest: a registered owner, a resident, or a pool of people matching a set of filters.

All four lookup types are gated behind a single `ownership` entitlement on your API key and billed the same way: you're only ever charged when a match is found.

| You have…             | You call…                   | You get back…                                                        |
| :-------------------- | :-------------------------- | :------------------------------------------------------------------- |
| A 17-character VIN    | `GET /v1/ownership/vin`     | The vehicle's registered owner(s), contact info, and vehicle history |
| A full name + address | `GET /v1/ownership/person`  | Contact details and any vehicle linked to that identity              |
| Just a street address | `GET /v1/ownership/address` | Everyone on file at that address, with optional enrichment           |
| A ZIP code + filters  | `GET /v1/ownership/zip`     | A page of matching people in that area                               |

<Note>
  Every response follows a strict **"charge only on non-empty results"** rule:
  if there's no match, you get a **404** with `error: "no_data"`, your usage
  counter doesn't move, and nothing is billed. Optional parameters that trigger
  a real, separately-billed lookup (like Address's `include=demographics`) are
  called out explicitly below — everything else is included in the base call.
</Note>

---

## VIN → Owner

Interactive reference: [Ownership by VIN](/api-reference/ownership/ownership-by-vin).

<Row>
  <Col>
    Look up the registered owner(s) of a vehicle by VIN, along with vehicle attributes, vehicle history, and contact details.

    ### Required attributes

    <Properties>
      <Property name="key" type="string">
        Your CarsXE API key.
      </Property>
      <Property name="vin" type="string">
        The 17-character vehicle identification number.
      </Property>
    </Properties>

    ### Optional attributes

    <Properties>
      <Property name="include" type="string">
        Comma-separated subset of `demographics,emails,phones,vehicle_history`. Omit it to get everything.
      </Property>
    </Properties>

    <Note>
      `vehicle_history`, `emails`, and `phones` come from the same call as everything else — including them costs nothing extra, and they're on by default. `demographics` is different: the field always **appears** in the response (empty by default), but it only gets **populated** when you explicitly pass `include=demographics`, because that triggers a second, separately-billed lookup.
    </Note>

    ---

    ### Response attributes

    <Properties>
      <Property name="success" type="boolean">
        Whether the request was processed successfully.
      </Property>
      <Property name="vin" type="string">
        The VIN you queried.
      </Property>
      <Property name="include" type="string">
        Echoes the `include` value you passed. Omitted entirely when you didn't pass one.
      </Property>
      <Property name="vehicle" type="object">
        Attributes for the queried vehicle. See the table below.
      </Property>
      <Property name="owners" type="array">
        One entry per person linked to this VIN. See the table below.
      </Property>
      <Property name="error" type="string">
        Machine-readable error code, or `""` on success.
      </Property>
    </Properties>

    #### `vehicle` object

    | Field | Type | Description |
    | :--- | :--- | :--- |
    | `make`, `model` | string | Vehicle make and model. |
    | `year` | number \| null | Model year. |
    | `manufacturer` | string | Full legal manufacturer name. |
    | `fuel_type`, `drive_type`, `transmission_type` | string | e.g. `Diesel`, `4WD`, `A`. |
    | `body_type`, `body_subtype` | string | e.g. `PICKUP`, `Crew Cab`. |
    | `doors`, `engine_cylinders` | number \| null | |
    | `vehicle_class`, `size`, `vehicle_type` | string | e.g. `Mainstream`, `Full-Size`, `TRUCK`. |

    #### `owners[]` object

    | Field | Type | Description |
    | :--- | :--- | :--- |
    | `record_id` | string | Internal identity ID for this person. |
    | `first_name`, `last_name` | string | |
    | `age`, `gender` | string | Empty when not on file. |
    | `address` | object | `{ street, city, state, zip }`. |
    | `demographics` | object | `marital_status`, `home_owner`, `children_in_household`, `veteran_in_household`, `occupation`, `income_range`, `net_worth_range`, `credit_range`. All empty/false unless `include=demographics` found a match. |
    | `emails[]` | array | `{ address, last_seen }`. |
    | `phones[]` | array | `{ number, type, dnc }`. |
    | `vehicle_history[]` | array | Up to 3 other vehicles linked to this owner: `{ make, model, year }`. |

    ### Errors

    | Status | `error` | Cause |
    | :--- | :--- | :--- |
    | 400 | `invalid_inputs` | Missing `vin`. |
    | 400 | `invalid_vin` | Not a well-formed 17-character VIN. |
    | 404 | `no_data` | No match — not billed. The opt-in demographics call is skipped entirely in this case. |

  </Col>
  <Col sticky>
    <CodeGroup title="Request" tag="GET" label="/v1/ownership/vin">
      ```bash
      curl -G https://api.carsxe.com/v1/ownership/vin \
        -d key=YOUR_API_KEY \
        -d vin=1FT8X3BT0BEA61538
      ```
    </CodeGroup>

    <CodeGroup title="Request — with opt-in demographics" tag="GET" label="/v1/ownership/vin">
      ```bash
      curl -G https://api.carsxe.com/v1/ownership/vin \
        -d key=YOUR_API_KEY \
        -d vin=1FT8X3BT0BEA61538 \
        -d include=demographics
      ```
    </CodeGroup>

    <CodeGroup title="Response — documentation sample VIN (includes populated demographics)">
      ```json
      {
        "success": true,
        "vin": "1FT8X3BT0BEA61538",
        "vehicle": {
          "make": "Ford",
          "model": "F-350",
          "year": 2011,
          "manufacturer": "Ford Motor Company",
          "fuel_type": "Diesel",
          "drive_type": "4WD",
          "transmission_type": "A",
          "body_type": "PICKUP",
          "body_subtype": "Crew Cab",
          "doors": 4,
          "engine_cylinders": 8,
          "vehicle_class": "Mainstream",
          "size": "Full-Size",
          "vehicle_type": "TRUCK"
        },
        "owners": [
          {
            "record_id": "2074367570",
            "first_name": "Mark",
            "last_name": "Spence",
            "age": "57",
            "gender": "Male",
            "address": {
              "street": "910 Lucabaugh Mill Rd",
              "city": "Westminster",
              "state": "MD",
              "zip": "21157"
            },
            "demographics": {
              "marital_status": "Married",
              "home_owner": true,
              "children_in_household": false,
              "veteran_in_household": false,
              "occupation": "President",
              "income_range": "$100,000 - $149,999",
              "net_worth_range": "$250,000 - $499,999",
              "credit_range": "700 - 749"
            },
            "emails": [{ "address": "mspence32@gmail.com", "last_seen": "2026-03-08" }],
            "phones": [{ "number": "4437890815", "type": "mobile", "dnc": true }],
            "vehicle_history": [{ "make": "Ford", "model": "Explorer", "year": 2015 }]
          }
        ],
        "error": ""
      }
      ```
    </CodeGroup>

    <Note>
      The sample VIN above returns a canned documentation response (before auth) with fully populated demographics so the complete shape is visible. For any other VIN, demographics stay empty unless you pass `include=demographics` as in the second request example.
    </Note>

  </Col>
</Row>

---

## Person → Contact Info

Interactive reference: [Ownership by person](/api-reference/ownership/ownership-by-person).

<Row>
  <Col>
    Resolve contact details for a specific person you already have a name and address for.

    ### Required attributes

    <Properties>
      <Property name="key" type="string">
        Your CarsXE API key.
      </Property>
      <Property name="first_name" type="string">
        Max 50 characters.
      </Property>
      <Property name="last_name" type="string">
        Max 50 characters.
      </Property>
      <Property name="address" type="string">
        Street address only (no city/state) — max 100 characters.
      </Property>
      <Property name="zip" type="string">
        5-digit US ZIP, optionally ZIP+4.
      </Property>
    </Properties>

    ### Optional attributes

    <Properties>
      <Property name="include" type="string">
        Comma-separated subset of `emails,phones`. An unrecognized value is ignored, not rejected — you'll just get everything back.
      </Property>
    </Properties>

    ---

    ### Response attributes

    <Properties>
      <Property name="success" type="boolean">
        Whether the request was processed successfully.
      </Property>
      <Property name="input" type="object">
        Echo of the query you made — `first_name`, `last_name`, `address`, `zip`, plus `include` when you passed one.
      </Property>
      <Property name="count" type="number">
        Number of matches found.
      </Property>
      <Property name="matches" type="array">
        One entry per matched person. See the table below.
      </Property>
      <Property name="error" type="string">
        Machine-readable error code, or `""` on success.
      </Property>
    </Properties>

    #### `matches[]` object

    | Field | Type | Description |
    | :--- | :--- | :--- |
    | `record_id` | string | Internal identity ID for this person. |
    | `first_name`, `last_name` | string | |
    | `address` | object | `{ street, city, state, zip }` — `city`/`state` are the canonical values for the address, which may differ in formatting from what you sent. |
    | `vin` | string | A vehicle linked to this identity, or `""` when none. |
    | `emails[]` | array | `{ address, last_seen }`. Can be empty. |
    | `phones[]` | array | `{ number, type, dnc }`. Can be empty — don't assume a match has both emails and phones. |

    ### Errors

    | Status | `error` | Cause |
    | :--- | :--- | :--- |
    | 400 | `invalid_inputs` | Missing or oversized name/address. |
    | 400 | `invalid_zip` | Not a valid 5-digit (or ZIP+4) US ZIP. |
    | 404 | `no_data` | No match — not billed. |

  </Col>
  <Col sticky>
    <CodeGroup title="Request" tag="GET" label="/v1/ownership/person">
      ```bash
      curl -G https://api.carsxe.com/v1/ownership/person \
        -d key=YOUR_API_KEY \
        -d first_name=John \
        -d last_name=Sample \
        -d address="123 Example St" \
        -d zip=90210
      ```
    </CodeGroup>

    <CodeGroup title="Response">
      ```json
      {
        "success": true,
        "input": {
          "first_name": "John",
          "last_name": "Sample",
          "address": "123 Example St",
          "zip": "90210"
        },
        "count": 1,
        "matches": [
          {
            "record_id": "2074367570",
            "first_name": "John",
            "last_name": "Sample",
            "address": {
              "street": "123 Example St",
              "city": "Beverly Hills",
              "state": "CA",
              "zip": "90210"
            },
            "vin": "",
            "emails": [
              { "address": "john.sample@gmail.com", "last_seen": "" },
              { "address": "jsample@msn.com", "last_seen": "" }
            ],
            "phones": [
              { "number": "3105551901", "type": "", "dnc": false },
              { "number": "3105558018", "type": "", "dnc": false }
            ]
          }
        ],
        "error": ""
      }
      ```
    </CodeGroup>

  </Col>
</Row>

---

## Address → Residents

Interactive reference: [Ownership by address](/api-reference/ownership/ownership-by-address).

<Row>
  <Col>
    Find everyone on file at a street address, with optional vehicle history, compliance-grade Do-Not-Call flags, or household demographics.

    ### Required attributes

    <Properties>
      <Property name="key" type="string">
        Your CarsXE API key.
      </Property>
      <Property name="address" type="string">
        Street address only, max 100 characters.
      </Property>
      <Property name="zip" type="string">
        5-digit US ZIP, optionally ZIP+4.
      </Property>
    </Properties>

    ### Optional attributes

    <Properties>
      <Property name="variant" type="string">
        `vehicle_history` or `compliance` — mutually exclusive, pick one. An unrecognized value is **rejected with 400**, not silently ignored.
      </Property>
      <Property name="include" type="string">
        Only recognized value: `demographics`. Also rejected with 400 if garbled — it triggers a second, billed lookup, so typos don't fail silently.
      </Property>
    </Properties>

    | `variant` | Adds | When to use it |
    | :--- | :--- | :--- |
    | *(omit it)* | Baseline identity + contact fields | You just need who's there and how to reach them. |
    | `vehicle_history` | Up to 3 vehicles historically linked to each match | You care about what they've owned, not just contact info. |
    | `compliance` | Real Do-Not-Call flags + a linked VIN | You're about to call or text and need to honor DNC status. |

    <Note>
      Unlike `include` on VIN and Person, both `variant` and `include` here each select a specific, separately-billed vendor call — so an unrecognized value is rejected outright with a `400` instead of silently falling back to a default.
    </Note>

    ---

    ### Response attributes

    <Properties>
      <Property name="success" type="boolean">
        Whether the request was processed successfully.
      </Property>
      <Property name="input" type="object">
        Echo of the query you made — `address`, `zip`, plus `variant`/`include` when you passed them.
      </Property>
      <Property name="count" type="number">
        Number of matches found.
      </Property>
      <Property name="matches" type="array">
        One entry per matched resident. See the table below.
      </Property>
      <Property name="error" type="string">
        Machine-readable error code, or `""` on success.
      </Property>
    </Properties>

    #### `matches[]` object

    | Field | Type | Description |
    | :--- | :--- | :--- |
    | `record_id` | string | Internal identity ID for this person. |
    | `first_name`, `last_name` | string | |
    | `address` | object | `{ street, city, state, zip }`. |
    | `emails[]` | array | `{ address, last_seen }`. |
    | `phones[]` | array | `{ number, type, dnc }` — `dnc` is only real with `variant=compliance`; otherwise `false`. |
    | `vin` | string | Present only with `variant=compliance`. |
    | `vehicle_history[]` | array | Present only with `variant=vehicle_history`: up to 3 `{ make, model, year }` entries. |
    | `demographics` | object | Present only with `include=demographics` **and** a match was found: `age`, `gender`, `marital_status`, `credit_range`, `home_owner`, `income_hh`, `net_worth_hh`, `children_hh`, `occupation`, `veteran_hh`. |

    <Note>
      `demographics` is capped at **one enriched match per address** — a limit in the underlying dataset, not something this API can lift. On a multi-resident address, at most one match ever carries a `demographics` object.
    </Note>

    ### Errors

    | Status | `error` | Cause |
    | :--- | :--- | :--- |
    | 400 | `invalid_inputs` | Missing/oversized address, invalid `variant`, or invalid `include`. |
    | 400 | `invalid_zip` | Not a valid 5-digit (or ZIP+4) US ZIP. |
    | 404 | `no_data` | No match on the primary lookup — not billed. |

  </Col>
  <Col sticky>
    <CodeGroup title="Request" tag="GET" label="/v1/ownership/address">
      ```bash
      curl -G https://api.carsxe.com/v1/ownership/address \
        -d key=YOUR_API_KEY \
        -d address="123 Example St" \
        -d zip=90210
      ```
    </CodeGroup>

    <CodeGroup title="Request — compliance variant + demographics" tag="GET" label="/v1/ownership/address">
      ```bash
      curl -G https://api.carsxe.com/v1/ownership/address \
        -d key=YOUR_API_KEY \
        -d address="27 Cobble Creek Dr" \
        -d zip=08057 \
        -d variant=compliance \
        -d include=demographics
      ```
    </CodeGroup>

    <CodeGroup title="Response — baseline">
      ```json
      {
        "success": true,
        "input": {
          "address": "123 Example St",
          "zip": "90210"
        },
        "count": 2,
        "matches": [
          {
            "record_id": "2074367570",
            "first_name": "John",
            "last_name": "Sample",
            "address": { "street": "123 Example St", "city": "Beverly Hills", "state": "CA", "zip": "90210" },
            "emails": [{ "address": "john.sample@gmail.com", "last_seen": "" }],
            "phones": [{ "number": "3105551901", "type": "", "dnc": false }]
          },
          {
            "record_id": "7304690614",
            "first_name": "Jane",
            "last_name": "Sample",
            "address": { "street": "123 Example St", "city": "Beverly Hills", "state": "CA", "zip": "90210" },
            "emails": [{ "address": "jane.sample@yahoo.com", "last_seen": "" }],
            "phones": [{ "number": "3105558018", "type": "", "dnc": false }]
          }
        ],
        "error": ""
      }
      ```
    </CodeGroup>

    <CodeGroup title="Response — variant=compliance + include=demographics">
      ```json
      {
        "success": true,
        "input": {
          "address": "27 Cobble Creek Dr",
          "zip": "08057",
          "variant": "compliance",
          "include": "demographics"
        },
        "count": 1,
        "matches": [
          {
            "record_id": "3319048827",
            "first_name": "Renee",
            "last_name": "Castillo",
            "address": { "street": "27 Cobble Creek Dr", "city": "Moorestown", "state": "NJ", "zip": "08057" },
            "emails": [{ "address": "renee.castillo@example.com", "last_seen": "" }],
            "phones": [{ "number": "5550142", "type": "", "dnc": true }],
            "vin": "1GKS2AKC1FR509821",
            "demographics": {
              "age": "56",
              "gender": "Male",
              "marital_status": "Married",
              "credit_range": "B. 750-799",
              "home_owner": "Home Owner",
              "income_hh": "O. $250K +",
              "net_worth_hh": "J. Greater than $499,999",
              "children_hh": "1",
              "occupation": "",
              "veteran_hh": ""
            }
          }
        ],
        "error": ""
      }
      ```
    </CodeGroup>

  </Col>
</Row>

---

## ZIP → Area Search

Interactive reference: [Ownership by ZIP](/api-reference/ownership/ownership-by-zip).

<Row>
  <Col>
    Search a broader area for people matching optional gender, age, and income filters. This is the only one-to-many, paginated lookup in the product.

    ### Required attributes

    <Properties>
      <Property name="key" type="string">
        Your CarsXE API key.
      </Property>
      <Property name="zip" type="string">
        Exactly 5 digits.
      </Property>
    </Properties>

    ### Optional attributes

    <Properties>
      <Property name="gender" type="string">
        `M` or `F`, case-insensitive.
      </Property>
      <Property name="min_age" type="string">
        Whole number. Optional — only forwarded upstream when provided (CarsXE does not apply a default).
      </Property>
      <Property name="max_age" type="string">
        Whole number. Optional — only forwarded upstream when provided (CarsXE does not apply a default).
      </Property>
      <Property name="income" type="string">
        Full label, letter code, or a loose case/whitespace variant of either. See the table below.
      </Property>
      <Property name="page" type="string">
        Default `1`.
      </Property>
      <Property name="limit" type="string">
        Default `15`, max `100`.
      </Property>
    </Properties>

    #### Valid `income` values

    Pass the full string, the letter code alone, or a sloppy variant of either — `f`, `F. $50,000-$59,999`, and `  f  ` all resolve to the same bucket.

    | Code | Full value |
    | :--- | :--- |
    | — | `Unknown` |
    | `A` | Under $10,000 |
    | `B` | $10,000–$19,999 |
    | `C` | $20,000–$29,999 |
    | `D` | $30,000–$39,999 |
    | `E` | $40,000–$49,999 |
    | `F` | $50,000–$59,999 |
    | `G` | $60,000–$74,999 |
    | `H` | $75,000–$99,999 |
    | `K` | $100,000–$149,999 |
    | `L` | $150,000–$174,999 |
    | `M` | $175,000–$199,999 |
    | `N` | $200,000–$249,999 |
    | `O` | $250K + |

    ---

    ### Response attributes

    <Properties>
      <Property name="success" type="boolean">
        Whether the request was processed successfully.
      </Property>
      <Property name="zip" type="string">
        The ZIP you queried.
      </Property>
      <Property name="filters" type="object">
        Only the filters you actually set — not the resolved defaults.
      </Property>
      <Property name="page" type="number">
        Current page.
      </Property>
      <Property name="limit" type="number">
        Page size.
      </Property>
      <Property name="count" type="number">
        Number of records on this page.
      </Property>
      <Property name="records" type="array">
        One entry per matched person. See the table below.
      </Property>
      <Property name="error" type="string">
        Machine-readable error code, or `""` on success.
      </Property>
    </Properties>

    #### `records[]` object

    | Field | Type | Description |
    | :--- | :--- | :--- |
    | `record_id` | string | |
    | `first_name`, `last_name` | string | |
    | `age`, `gender` | string | Usually blank — these are filter **inputs**, not guaranteed per-record output. Use VIN or Person if you need a confirmed value. |
    | `address` | object | `{ street, city, state, zip }`. |
    | `vin` | string | Linked VIN, or `""` when none. |
    | `vehicle` | object \| null | `{ make, model, year }`, or `null` when no vehicle is linked. |
    | `emails[]` | array | `{ address }`. |
    | `phones[]` | array | `{ number, dnc }`. |
    | `demographics` | object | `credit_range`, `education`, `home_owner`, `income_hh`, `marital_status`, `net_worth_hh`, `num_adults_hh`, `num_children_hh`, `occupation_type`. Frequently blank — this is a broad-search endpoint, not every record has every attribute on file. |

    ### Errors

    | Status | `error` | Cause |
    | :--- | :--- | :--- |
    | 400 | `invalid_zip` | Missing or not exactly 5 digits. |
    | 400 | `invalid_gender` | Not `M`/`F` after normalization. |
    | 400 | `invalid_age` | `min_age`/`max_age` not a whole number. |
    | 400 | `invalid_income` | Doesn't match any known code or label. |
    | 404 | `no_data` | No records match — not billed. |

  </Col>
  <Col sticky>
    <CodeGroup title="Request" tag="GET" label="/v1/ownership/zip">
      ```bash
      curl -G https://api.carsxe.com/v1/ownership/zip \
        -d key=YOUR_API_KEY \
        -d zip=00000 \
        -d gender=f \
        -d min_age=45
      ```
    </CodeGroup>

    <CodeGroup title="Response">
      ```json
      {
        "success": true,
        "zip": "00000",
        "filters": {},
        "page": 1,
        "limit": 15,
        "count": 1,
        "records": [
          {
            "record_id": "2104840276",
            "first_name": "Victoria",
            "last_name": "Rose",
            "age": "34",
            "gender": "F",
            "address": {
              "street": "141 Hardwood Ln SE",
              "city": "Kalkaska",
              "state": "MI",
              "zip": "49646"
            },
            "vin": "1HGBH41JXMN109186",
            "vehicle": { "make": "Honda", "model": "Civic", "year": 2021 },
            "emails": [{ "address": "victoria.rose@example.com" }, { "address": "vrose2@gmail.com" }],
            "phones": [
              { "number": "2314567890", "dnc": false },
              { "number": "2319876543", "dnc": true }
            ],
            "demographics": {
              "credit_range": "H. 700-749",
              "education": "Some College",
              "home_owner": "Yes",
              "income_hh": "F. $50,000-$59,999",
              "marital_status": "Married",
              "net_worth_hh": "D. $50,000-$99,999",
              "num_adults_hh": "2",
              "num_children_hh": "1",
              "occupation_type": "Professional"
            }
          }
        ],
        "error": ""
      }
      ```
    </CodeGroup>

  </Col>
</Row>

---

## Shared behavior

**Billing.** All four lookups follow the same rule: zero records means a `404` with `error: "no_data"`, no usage increment, and no charge. You're only billed on a response that actually returns data.

**Every response tells you what request produced it.** Optional parameters that shape the response — `include` on VIN and Person, `variant` and `include` together on Address — are echoed back whenever they're set, and simply omitted when they're not. Useful for auditing which (separately-priced) enrichment actually ran.

**`include` isn't one concept.** On VIN and Person it only decides which already-fetched fields to show, so an unrecognized value is ignored and falls back to showing everything. On Address, `include=demographics` (and `variant`) each select a real, separately-billed lookup — so an unrecognized value is rejected with `400` instead.

---

## Error codes

| Status    | Meaning                                                                                                                  | Seen on  |
| :-------- | :----------------------------------------------------------------------------------------------------------------------- | :------- |
| 200       | Success — at least one match found.                                                                                      | All four |
| 400       | Malformed input — fix the request before retrying.                                                                       | All four |
| 401       | Missing/invalid API key, or an inactive account.                                                                         | All four |
| 403       | `api_not_enabled` — your key doesn't have the `ownership` entitlement.                                                   | All four |
| 404       | `no_data` — valid request, zero matches, not billed.                                                                     | All four |
| 429       | Usage limit reached for your plan.                                                                                       | All four |
| 503       | Kill-switch — Ownership temporarily unavailable. Body is `{ success: false, message: "The Ownership API is temporarily unavailable." }` (no `error` code). | All four |
| 408 / 500 | Upstream timeout or vendor error — safe to retry.                                                                        | All four |

<FAQ faqs={[
  { question: "What is the Ownership API?",
  answer: "One product with four lookup types — VIN, Person (name + address), Address, and ZIP — that all resolve people and contact details from CarsXE's identity graph. They share a single entitlement and billing model."},

{ question: "Which endpoint should I use?",
answer: <ul><li>Have a VIN? Use <code>VIN</code>.</li><li>Have a full name and address? Use <code>Person</code>.</li><li>Only have an address? Use <code>Address</code>.</li><li>Have a ZIP code and want a filtered list of people in that area? Use <code>ZIP</code>.</li></ul>},

{ question: "Do I get charged if there's no match?",
answer: "No. A 404 with error: \"no_data\" means the API correctly found nothing — it's not billed and doesn't count against your usage."},

{ question: "What's the difference between variant and include on the Address endpoint?",
answer: "variant picks which baseline schema you get back (vehicle history or compliance-grade DNC flags) — pick one. include=demographics is an additive enrichment layered on top of either. Both trigger a distinct, separately-billed lookup, so an invalid value returns 400 rather than being silently ignored."},

{ question: "Why is demographics empty even though I asked for it?",
answer: "On VIN and Address, the demographics enrichment can come back with no data for a specific VIN or address even though the primary lookup succeeded — it's a separate dataset with its own, narrower coverage. An empty demographics object after explicitly requesting it means there's nothing on file, not an error."},

{ question: "Can a VIN or address resolve to more than one person?",
answer: "Yes — co-owners, prior owners still on file, roommates, or family members can all be legitimately linked to the same VIN or address. Always iterate the full owners/matches array rather than assuming the first entry is the only answer."},

{ question: "Why are age and gender blank on ZIP search results?",
answer: "On the ZIP endpoint, age and gender are filter inputs, not guaranteed per-record output fields. If you need a confirmed age or gender for a specific person, use VIN or Person instead."},

{ question: "Does this API require authentication?",
answer: "Yes. All four endpoints require your CarsXE API key as the key query parameter, and your key must have the ownership entitlement enabled."}
]} hidePadding />

## Sitemap

See the full [sitemap](/sitemap.md) for all pages.
Docs-scoped sitemap: [/docs/sitemap.md](/docs/sitemap.md).
Well-known sitemap: [/.well-known/sitemap.md](/.well-known/sitemap.md).