Auth: X-API-KEY: <your key> header
Use when: The user gives you an address and wants a valuation or loan quote.
Don't use when: You already have the county id and parcel id (APN). Go straight to createProperty.
Parameters
| Name |
In |
Type |
Required |
Description |
address |
query |
string |
yes |
Full street address, including city, state and ZIP when known. |
Notes for agents
matchedAddress is the address the geocoder actually matched. If it differs meaningfully from what the user typed, confirm before continuing.
- One address can return several parcels. If there is more than one, show the user the options (property type, units, size) and let them choose. Do not pick silently.
- A
404 or an empty parcels array means no parcel was found at the matched address, and a 400 means the address could not be geocoded. In each case ask the user for a more complete address or the APN.
Example request
curl -G https://app.smartcapitalcenter.com/api/v2/public/valuation/parcels \
-H "X-API-KEY: $SCC_API_KEY" \
--data-urlencode "address=123 Main St, Los Angeles, CA 90012"
Response 200
OK.
Standard envelope with data containing:
| Field |
Type |
Description |
matchedAddress |
string |
The address Google matched for the query. |
parcels |
array |
Candidate parcels at the matched address. |
parcels[].countyId |
string |
County id (5-digit FIPS code) — pass to create-property. Example: 06037. |
parcels[].parcelId |
string |
Parcel id (APN) — pass to create-property. Example: 5555-012-034. |
parcels[].propertyType |
string |
Property type. |
parcels[].units |
integer |
Number of units, if known. |
parcels[].size |
integer |
Building size in sqft, if known. |
Errors
| Code |
Meaning |
| 400 |
Address could not be geocoded |
| 404 |
No parcels at the matched address |
Next: createProperty with the chosen parcel's countyId and parcelId.
# searchParcels
`GET /api/v2/public/valuation/parcels`
Looks up a street address and returns the land parcels at that location. Each parcel has the `countyId` and `parcelId` needed to create a property.
**Auth:** `X-API-KEY: <your key>` header
**Use when:** The user gives you an address and wants a valuation or loan quote.
**Don't use when:** You already have the county id and parcel id (APN). Go straight to `createProperty`.
## Parameters
| Name | In | Type | Required | Description |
|---|---|---|---|---|
| `address` | query | string | yes | Full street address, including city, state and ZIP when known. |
## Notes for agents
- `matchedAddress` is the address the geocoder actually matched. If it differs meaningfully from what the user typed, confirm before continuing.
- One address can return several parcels. If there is more than one, show the user the options (property type, units, size) and let them choose. Do not pick silently.
- A `404` or an empty `parcels` array means no parcel was found at the matched address, and a `400` means the address could not be geocoded. In each case ask the user for a more complete address or the APN.
## Example request
```bash
curl -G https://app.smartcapitalcenter.com/api/v2/public/valuation/parcels \
-H "X-API-KEY: $SCC_API_KEY" \
--data-urlencode "address=123 Main St, Los Angeles, CA 90012"
```
## Response `200`
OK.
Standard envelope with `data` containing:
| Field | Type | Description |
|---|---|---|
| `matchedAddress` | string | The address Google matched for the query. |
| `parcels` | array | Candidate parcels at the matched address. |
| `parcels[].countyId` | string | County id (5-digit FIPS code) — pass to create-property. Example: `06037`. |
| `parcels[].parcelId` | string | Parcel id (APN) — pass to create-property. Example: `5555-012-034`. |
| `parcels[].propertyType` | string | Property type. |
| `parcels[].units` | integer | Number of units, if known. |
| `parcels[].size` | integer | Building size in sqft, if known. |
## Errors
| Code | Meaning |
|---|---|
| 400 | Address could not be geocoded |
| 404 | No parcels at the matched address |
**Next:** `createProperty` with the chosen parcel's `countyId` and `parcelId`.