You can now specify a minimum number of contiguous panels in a row (rack) in AutoDesigner API. Increasing this number can reduce the cost of installation and the aesthetic appeal of your system. However, keep in mind that Energy Mode already optimizes production and cost, and avoids having rows with very few panels when possible. If you make the minimum too high, it might result in a less than optimal system or even make it impossible to meet your energy target.
API versioning offers your developers a predictable path to API upgrades while allowing Aurora to evolve our platform without impacting your existing API-based integrations. With Versions API,
Aurora-API-Version HTTP header, and versioned API docs you will be able to self-manage our REST API version upgrades moving forward.
With this enhancement, you will get the best available imagery loaded by default for projects created via the Aurora API. No need to assign an owner to a project to obtain high-resolution images.
You can now programmatically retrieve leads created with Lead Capture AI and convert them into projects. The new API endpoints are accompanied by three webhook events:
lead_converted. With the new APIs and webhook events, you can keep your IT ecosystem (e.g., CRM) synchronized with lead information in Aurora in real-time. Note that you have to be on the Aurora Custom plans to access APIs and webhooks.
You can now specify a minimum and maximum roof face azimuth (in degrees, where 0 is north and 180 is south) upon which panels are allowed to be placed. This gives you more control over customizing your output, but is not necessary to produce an optimal system (i.e., Energy Mode will already avoid placing panels on shaded faces).
You can modify the following fields with Update Project API now in addition to the existing six fields.
You can now customize panel tilt, spacing, and orientation depending on whether a roof face is flat or pitched in order to align with your design and installation best practices and maximize irradiance and system production.
With the Retrieve Asset endpoint, you can retrieve details of an individual asset (e.g., screenshot). You will likely want to use the Retrieve Asset endpoint to look up asset details including URLs on receipt of
We added two new webhook events:
asset_created. The consumption profile webhook event fires upon any change to a consumption profile in Aurora. The asset webhook event fires when an asset (e.g., screenshot, DXF file) is created and ready for download in Aurora. With the two new webhooks, you can keep applications in your IT ecosystem in sync with Aurora in real-time.
We updated our API Reference to show a full list of HTTP responses that you might receive for each endpoint. With the list of responses, you can build better quality integrations with Aurora by proactively handling error states in your code.