You can now view Aurora API version that your token is pinned to in the Aurora UI. With easily accessible version information, your developers (and Aurorans helping them) can root cause issues related to versioning faster.

You can now access initial_monthly_avoided_cost and has_uploaded_utility_bill fields via Retrieve Lead endpoint. The initial_monthly_avoided_cost field signifies one month of savings based on year one (unescalated) savings amount. The has_uploaded_utility_bill is set to true if a homeowner has uploaded a utility bill for a Lead Capture AI lead. With the additional fields, you can streamline your solar workflows as well as power email and text campaigns by data from Lead Capture AI.

You can use restricted API keys to grant micro-services (internally-developed or third-party) access to your data in Aurora. Restricted keys grant access to only a specified subset of API end points for your tenant (e.x., only List and Retrieve Projects). And you can have multiple restricted keys with varying levels of access. To generate a restricted key, please contact your Aurora Account team and provide a list of API endpoints that you want the key to have access to.

You can list partners - partner ids and partner names - configured in your tenant using List Partners endpoint. With partner management in Aurora, you can organize sales dealers into separate spaces with custom settings such as logos and base prices per watt.

You can now assign users to partners by supplying partner_id in Create User and Invite User API calls. List Users endpoint also comes with partner_id filter now so you can list all users assigned to a partner in one API call. Lastly, you can lookup if and which partner a user has been assigned to using Retrieve User endpoint.

You can now assign projects to a partner by supplying partner_id in Create Project API calls. If no partner_id is provided on project creation, partner_id will default to the partner of the owner_id if the project owner belongs to a partner. In addition, you can lookup if and which partner a project has been assigned to using Retrieve Project endpoint.

You can now retrieve the length of all roof edges in a design via the Roof Summary API, allowing you to deliver more accurate roofing quotes directly from your Aurora model. On each roof in design, the edges_length field will contain the total length of five edge types (eave, hip, rake, ridge, valley).

You can set preferred solar panel(s) for a project via Create Projector Update Project endpoints now. With the preferred panels set, you can be sure that your sales team will only sell panels appropriate for the site location, avoiding potentially deal-breaking change orders. AutoDesigner will use preferred panels in both Design Mode and Sales Mode. If no preferred panels are set, AutoDesigner will use panels enabled in your tenant.

We fixed an error where we previously required a tenant Admin to be on the project’s assigned Team. Now, Aurora does not validate that a tenant Admin with owner_id belongs to the team with team_id when you make calls to Project Create and Project Update endpoints.

When using Teams, Aurora now validates that the owner with owner_id is a valid user in your tenant when you make calls to Project Create and Project Update endpoints. This validation assures that your users indeed can see projects that you want them to see.