eagleview

™

WebServices

Introduction

Welcome to EagleView's REST WebServices documentation!

This documentation will walk you through the entire roof measurement order process.
Please direct any questions you may have to Integrations@EagleView.com

Endpoint

The endpoint for the test integrations environment is https://webservices-integrations.eagleview.com

Note: For those integrating via developer.eagleview.com, the sandbox endpoint
is https://sandbox.apicenter.eagleview.com

Authentication

EagleView leverages OAuth2 Token Authentication for all API calls. Each call must contain a token header. Tokens can be refreshed using a refresh token. Refresh tokens are single use, but a new refresh token is issued when a new bearer token is issued. Access tokens are valid for 24 hours after issue. Refresh tokens are valid for 30 days after issue.

Note: For those integrating via developer.eagleview.com, please reference the authentication
instructions here

Ordering

The EagleView ordering process offers many API methods which allow for varying degrees of customization. Ordering in the first step in the EagleView roof measurement process as it kickstarts the report creation process.

Order Status

Once the report has been created in the Ordering stage, it is possible to query the status of the order via Order Status API methods.

Order Adjustments

Occasionally, a report will need to be adjusted by the customer before it can continue processing. This could be due to a necessary upgrade/downgrade due to the image quality availble.

Retrieving Files

Once a report has completed processing, it is possible to retrieve it via Retrieving Files API methods.