With the List and Retrieve DC Optimizers APIs, you can get the name, manufacturer, output voltage, efficiency, maximum efficiency and spec sheets for DC optimizers used in your tenant, either individually or in list format.

With the List and Retrieve Inverters APIs, you can get the name, manufacturer, rating, output voltage, efficiency, weight, and spec sheet for inverters used in your tenant, either individually or in list format.

With the List and Retrieve Modules APIs, you can get the name, manufacturer, rating, dimensions, weight, and spec sheets for modules used in your tenant, either individually or in list format.

With the Aurora API Client App, you can get an X-Ray view into the data underlying your Aurora design directly within Design Mode. Powered by Sync API, the API Client shows API responses for your project and design, so you can quickly troubleshoot issues with your API-powered workflows.

You can now change a design’s name with Update Design API. This capability enables you to name designs to reflect specific information (e.g., kit used), and sync that information between Aurora and other apps in your IT ecosystem.

With Retrieve Design API, you can retrieve basic design information including name. If your Aurora design names include meaningful project data such as kit size, revisions, or instructions, you can now push that information to the rest of your IT ecosystem.

You can now view the parsed components of the property_address in Retrieve Project API, including street_address, city, region, postal_code, and country. With the postal_code component, for example, you can apply logic in your IT ecosystem that leverages a property’s zip code without the need to parse property_address first.

Aurora released a new API version to make backward-incompatible changes. To avoid disrupting your integration and breaking your code, we don’t change your version automatically. When you are ready, you can upgrade to the latest version in Aurora settings, or by using Versions API. The following are breaking changes in version 2024.05.

You can now subscribe to the design_request_created webhook event. The webhook payload can include <DESIGN_REQUEST_ID> and <SOURCE>, and it can be filtered on source. This webhook event will fire when a design request is created in the Aurora app or via API, enabling your IT ecosystem (e.g., CRM) to keep design request data in sync.

With the <SOURCE> URL parameter in the auto_designer_job_completed, fire_pathway_placement_job_completed, panel_irradiance_analysis_job_completed and performance_simulation_job_completed webhooks, you can ensure your Design API integration is triggered by machine (rather than user) actions.