EagleView Request Property Summary Data API
The Request Property Summary Data API from EagleView — 1 operation(s) for request property summary data.
The Request Property Summary Data API from EagleView — 1 operation(s) for request property summary data.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.curl "https://apis.io/api/v1/apis/eagleview:eagleview-request-property-summary-data-api"
curl "https://apis.io/api/v1/apis?limit=25"
Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
openapi: 3.2.0
info:
version: 0.0.1
title: Property Data Request Property Summary Data API
description: '# Introduction
## About
EagleView''s Property Data API provides data elements that characterize the composition and condition of a requested property.'
servers:
- url: https://apis.eagleview.com
description: Basepath
tags:
- name: Request Property Summary Data
paths:
/property-summary/v2/request:
post:
tags:
- Request Property Summary Data
security:
- bearerAuth: []
summary: Request Property Summary Data with Address or Coordinate
description: Submit a property data summary request by providing addresses or geographic coordinates. The endpoint accepts multiple addresses or coordinates, with a current limit of 20 addresses per request. This endpoint starts an asynchronous process to generate summary data using EagleView's models. You will receive a request ID and a 202 Accepted response. Use this ID to check the status or retrieve results with the GET /property-summary/v2/result/{requestId} endpoint. Optionally, provide a callback URL to receive results automatically when ready.
operationId: POST/property-summary/v2/request
requestBody:
required: true
content:
application/json:
schema:
type: object
required:
- input
properties:
input:
type: object
required:
- addresses
properties:
addresses:
type: array
maxItems: 20
minItems: 1
items:
oneOf:
- $ref: '#/components/schemas/SummarySingleLineAddressRequest'
- $ref: '#/components/schemas/SummaryMultiLineAddressRequest'
- $ref: '#/components/schemas/SummaryLatLonRequest'
callbackUrl:
type: string
example: https://api.example.com/callback
examples:
case1:
summary: SingleLine Address Request Body
value:
input:
addresses:
- address:
completeAddress: 3324 W TUCKER RD, BOISE, ID 83703, United States
refId: abc123
callbackUrl: https://api.example.com/callback
case2:
summary: US Multiline Address Request Body
value:
input:
addresses:
- address:
street: 3324 W TUCKER RD
city: BOISE
state: ID
zip: '83703'
country: US
refId: abc123
callbackUrl: https://api.example.com/callback
case3:
summary: Canadian Address Request Body
value:
input:
addresses:
- address:
street: 189 Brookside Dr
city: Toronto
province: 'ON'
postal: M4E 2M5
country: CA
refId: abc456
callbackUrl: https://api.example.com/callback
case4:
summary: Global Address Request Body (UK)
value:
input:
addresses:
- address:
line1: 33 Kingsway
locality: London
admin1: London
postal: WC2B 6UF
country: GB
refId: abc789
callbackUrl: https://api.example.com/callback
case5:
summary: Lat Lon Request Body
value:
input:
addresses:
- coordinates:
lat: 43.6532
lon: -116.312
refId: abc123
callbackUrl: https://api.example.com/callback
callbacks:
Get job status Callback:
'{$requestBody.callbackUrl}':
post:
requestBody:
description: The callback is a POST request with the results json payload.
content:
application/json:
schema:
$ref: '#/components/schemas/SummaryResponse'
responses:
'200':
description: Your server implementation should return this HTTP status code if the data was received successfully
responses:
'202':
description: Accepted
content:
application/json:
schema:
$ref: '#/components/schemas/PostSummaryRequestResponse'
'400':
description: Bad Request
content:
application/json:
schema:
$ref: '#/components/schemas/model.Error'
'401':
description: Unauthorized
content:
application/json:
schema:
$ref: '#/components/schemas/model.Error'
'403':
description: Forbidden
content:
application/json:
schema:
$ref: '#/components/schemas/model.Error'
'422':
description: Unprocessable Entity
content:
application/json:
schema:
$ref: '#/components/schemas/model.Error'
'429':
description: Too Many Requests
content:
application/json:
schema:
$ref: '#/components/schemas/model.Error'
'500':
description: Internal Server Error
content:
application/json:
schema:
$ref: '#/components/schemas/model.Error'
'503':
description: Service Unavailable
x-operation-id-source: normalized
x-operation-id-original: POST /property-summary/v2/request
components:
schemas:
SummaryResponse:
type: object
properties:
request:
type: object
properties:
id:
type: string
example: 5decd115-771d-4fcc-9d13-0e357a1cacb3
description: System-generated request_id that uniquely identifies the POST request
status:
type: string
example: Completed
description: 'Processing state of the request. Possible values: ''In Progress'', ''Complete'', ''Failure'''
results:
type: array
items:
type: object
properties:
input:
type: object
properties:
refId:
type: string
example: abc123
description: User-provided reference ID to correlate requests with responses
address:
type: object
properties:
completeAddress:
type: string
example: 10800 NE 8th St, Bellevue, WA 98004, US
description: The complete address string used as input for the query
refId:
type: string
example: abc123
description: User-provided reference_id to correlate requests with responses
response_address:
type: object
properties:
full_address:
type: string
example: 10800 NE 8th St, Bellevue, WA 98004, US
description: The full text address of the property. Address string is standardized through geocoding/reverse-geocoding.
line1:
type: string
example: 10800 NE 8th St
description: The street address of the property. Address string is standardized through geocoding/reverse-geocoding.
locality:
type: string
example: Bellevue
description: The city of the property. Address string is standardized through geocoding/reverse-geocoding.
admin1:
type: string
example: WA
description: The state of the property. Address string is standardized through geocoding/reverse-geocoding.
zip:
type: string
example: '98004'
description: The zip code of the property. Address string is standardized through geocoding/reverse-geocoding.
country:
type: string
example: US
description: The country code of the property. Address string is standardized through geocoding/reverse-geocoding.
response_coordinates:
type: object
properties:
lat:
type: number
example: 47.617746
description: Latitude geo-coordinate of the property in EPSG:4326 format, which is EGS sanitized
lon:
type: number
example: -122.195759
description: Longitude geo-coordinate of the property in EPSG:4326 format, which is EGS sanitized
roof_condition_rating:
type: object
properties:
value:
type: string
description: Roof condition rating value.
example: green
enum:
- green
- yellow
- red
imagery_date:
type: string
description: Date when the image was captured for this assessment (YYYY-MM-DD format)
example: '2024-12-20'
roof_solar_panel_presence:
type: object
properties:
value:
type: string
description: Solar panel presence indicator.
example: 'yes'
enum:
- 'yes'
- 'no'
- unknown
imagery_date:
type: string
description: Date when the image was captured for this assessment (YYYY-MM-DD format)
example: '2024-12-20'
roof_material:
type: object
properties:
value:
type: string
description: Roof material type.
example: shingle
enum:
- shingle
- wood shingle
- other
imagery_date:
type: string
description: Date when the image was captured for this assessment (YYYY-MM-DD format)
example: '2024-12-20'
info:
description: Metadata pertaining to the response payload when API is unable to deliver data. Possible values are - 'No data found', 'Invalid address', 'No building detected', 'Parcel geometry unavailable', 'ML model error' and 'No suitable imagery found'
type: object
properties:
code:
type: string
message:
type: string
SummaryMultiLineAddressRequest:
required:
- address
properties:
address:
description: 'Multi-line (form-field style) address supports multiple label sets to accommodate US-centric, Canada-centric, and global formats. Certain fields are treated as equivalent, and you may use any one label from each group.
The following fields are mandatory, and must be provided using at least one label from each group:
- Street address: ''street'' (US/Canada) or ''line1'' (global)
- City/locality: ''city'' (US/Canada) or ''locality'' (global)
- Administrative area: ''state'' (US) or ''province'' (Canada) or ''admin1'' (global)
- Postal code: ''zip'' (US) or ''postal'' (Canada/global)
The ''country'' field is optional, but recommended. Use the ''country'' label in all cases, and especially for addresses outside of US.
Although these labels can be used interchangeably within each group, the following conventions are recommended:
- For US addresses, use: ''street'', ''city'', ''state'', ''zip'', ''country''.
- For Canada addresses, use: ''street'', ''city'', ''province'', ''postal'', ''country''.
- For the rest of the world, use: ''line1'', ''locality'', ''admin1'', ''postal'', ''country''.
Using the region-appropriate labels improves clarity and makes your integrations easier to understand and maintain.'
type: object
required:
- street/line1
- city/locality
- state/province/admin1
- zip/postal
properties:
street/line1:
type: string
example: 3324 W TUCKER RD
city/locality:
type: string
example: BOISE
state/province/admin1:
type: string
example: ID
zip/postal:
type: string
example: '83703'
country:
type: string
example: US
refId:
type: string
example: abc123
SummarySingleLineAddressRequest:
required:
- address
properties:
address:
required:
- completeAddress
properties:
completeAddress:
type: string
example: 3324 W TUCKER RD, BOISE, ID 83703, United States
refId:
type: string
example: abc123
PostSummaryRequestResponse:
type: object
properties:
request:
type: object
properties:
href:
type: string
example: /property-summary/v2/result/5decd115-771d-4fcc-9d13-0e357a1cacb3
description: Relative URL path to retrieve the summary request results
id:
type: string
example: 5decd115-771d-4fcc-9d13-0e357a1cacb3
description: System-generated request ID that uniquely identifies the POST request
status:
type: string
example: In Progress
description: 'Processing state of the request. Possible values: ''In Progress'', ''Complete'', ''Failure'''
model.Error:
type: object
properties:
errorCode:
type: integer
description: Machine-readable code that identifies the type of error.
errorDescription:
type: string
description: Human-readable message that describes the error condition.
SummaryLatLonRequest:
required:
- coordinates
properties:
coordinates:
required:
- lat
- lon
properties:
lat:
type: number
example: 43.6532
lon:
type: number
example: -116.312
refId:
type: string
example: abc123
securitySchemes:
bearerAuth:
type: http
scheme: bearer
bearerFormat: JWT
x-tagGroups:
- name: PROPERTY DATA API
tags:
- Request Property Data
- Get Results
- Request Property Data (Bulk)
- Get Property Data (Bulk)
- name: IMAGE API
tags:
- Image Retrieval
- name: Property Summary Data API
tags:
- Request Property Summary Data
- Get Property Summary Data
- Request Property Summary Data (Bulk)
- Get Property Summary Data (Bulk)