Changelog

You can now upload, parse, and retrieve project utility bills through the Enterprise API. The Run Utility Bill Upload endpoint accepts a raw-binary body and dispatches an asynchronous parsing job, and the Retrieve Utility Bill Upload Status endpoint returns the job's progress. Once parsing completes, the List Utility Bills and Retrieve Utility Bill endpoints expose the parsed bill files on a project. Subscribe to the new utility_bill_upload_job_completed webhook event to be notified when a parsing job finishes (whether the bill was uploaded via API or via the in-app UI). The webhook payload supports <JOB_ID>, <UTILITY_BILL_ID>, <PROJECT_ID>, <STATUS>, and <SOURCE> URL attributes. Together, these endpoints enable fully automated utility bill ingestion workflows.

The agreement_status_changed webhook payload now includes <FINANCING_ID> and <DESIGN_ID> URL attributes. The financing ID corresponds to the selected financing option on the design. Both additions enable your downstream systems to associate agreement status changes with the correct design and financing product without making additional API calls.

You can now create and manage Docusign-based agreements through the Enterprise API. The new Run Agreement Download URL Generation endpoint enables programmatic agreement generation using Docusign as the e-signature provider. Subscribe to the agreement_download_url_job_completed webhook to be notified when a Docusign agreement job completes, enabling fully automated contract workflows within your sales pipeline.

You can now manage the full lifecycle of consumer orders through the Enterprise API. New Orders endpoints let you list and retrieve orders (including customer details and a temporary download URL for the consumer's utility bill), update an order's phase, decline an order, mark an order as sold, record activity events against an order, and asynchronously convert an order into an Aurora project. Subscribe to the order_created webhook to react in real time — the payload includes both <ORDER_ID> and <UTILITY_BILL_URL> so you can ingest the utility bill the moment an order arrives. The project_created webhook and project endpoints also carry the originating order_id, so you can trace any project back to its source order.

You can now run AI Roof using the Sync API. This feature is supported by the following endpoints and webhooks:

You can now submit interval data to the Update Consumption Profile API. The interval_data allows you to submit specific energy usage on 15, 30, or 60 minute intervals for a customer’s energy usage.

You can now subscribe to the milestone_created webhook event. The webhook payload can include <STAGE> and <SOURCE>, and it can be filtered on both. This webhook event will fire when a milestone is created in the Aurora app or via API, enabling your IT ecosystem (e.g., CRM) to keep data in sync or add automations based on a milestone event.

You can now programmatically generate a proposal PDF document for a design using the Run Proposal PDF Generation API. After generating a PDF, you can retrieve the result using the Proposal PDF Generation Status API.

You can now programmatically order EagleView Powered Models using the EagleView Design Request API. Placing an order for an EagleView Design Request resembles the existing workflow for Expert Design Requests via Aurora's Site Modeling service and similarly features auto-acceptance, webhooks, and mock requests.

You can assign users to partners by supplying partner_ids in Create User and Invite User API calls. The partner_id field is deprecated now. With this change, you can assigned a user to more than one Partner.