Auth: X-API-KEY: <your key> header
Use when: After searchParcels, or whenever you have a county id and parcel id.
Request body
Content type: application/json
| Field |
Type |
Required |
Description |
countyId |
string |
yes |
County id of the parcel (5-digit FIPS code). Example: 06037. |
parcelId |
string |
yes |
Parcel id (APN) within the county. Example: 5555-012-034. |
propertyName |
string |
no |
Optional display name for the property. Example: 123 Main St. |
Example request
curl -X POST https://app.smartcapitalcenter.com/api/v2/public/valuation/property \
-H "X-API-KEY: $SCC_API_KEY" \
-H "Content-Type: application/json" \
-d '{"countyId": "06037", "parcelId": "5555-012-034", "propertyName": "123 Main St"}'
Response 200
OK.
Standard envelope with data containing:
| Field |
Type |
Description |
propertyId |
integer |
Numeric property id — use this for uploads and valuation requests. Example: 123456. |
countyId |
string |
County id of the underlying parcel. |
parcelId |
string |
Parcel id (APN) of the underlying parcel. |
propertyName |
string |
The propertyName sent in this request, echoed back. An existing property keeps its stored name. |
Next: uploadDocument if the user has documents for the property, otherwise createOrder.
# createProperty
`POST /api/v2/public/valuation/property`
Registers a parcel as a property in the user's account and returns its numeric `propertyId`.
**Auth:** `X-API-KEY: <your key>` header
**Use when:** After `searchParcels`, or whenever you have a county id and parcel id.
## Request body
Content type: `application/json`
| Field | Type | Required | Description |
|---|---|---|---|
| `countyId` | string | yes | County id of the parcel (5-digit FIPS code). Example: `06037`. |
| `parcelId` | string | yes | Parcel id (APN) within the county. Example: `5555-012-034`. |
| `propertyName` | string | no | Optional display name for the property. Example: `123 Main St`. |
## Notes for agents
- Idempotent: if the property already exists, the existing one comes back unchanged. It is safe to retry.
- Keep the returned `propertyId`. Uploads and orders need it.
## Example request
```bash
curl -X POST https://app.smartcapitalcenter.com/api/v2/public/valuation/property \
-H "X-API-KEY: $SCC_API_KEY" \
-H "Content-Type: application/json" \
-d '{"countyId": "06037", "parcelId": "5555-012-034", "propertyName": "123 Main St"}'
```
## Response `200`
OK.
Standard envelope with `data` containing:
| Field | Type | Description |
|---|---|---|
| `propertyId` | integer | Numeric property id — use this for uploads and valuation requests. Example: `123456`. |
| `countyId` | string | County id of the underlying parcel. |
| `parcelId` | string | Parcel id (APN) of the underlying parcel. |
| `propertyName` | string | The `propertyName` sent in this request, echoed back. An existing property keeps its stored name. |
## Errors
| Code | Meaning |
|---|---|
| 400 | Validation error |
| 404 | Parcel not found |
**Next:** `uploadDocument` if the user has documents for the property, otherwise `createOrder`.