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.
When using Teams, on project creation via API, team_id will default to the team of the owner_id if the project owner belongs to only one team. With this change, you no longer have to explicitly set team_id, reducing the effort and complexity of your integration with Aurora.
You can now add filters to your webhook subscriptions in the Webhooks Dashboard. With webhook filters, you have fine control over which events in your Aurora tenant will notify your applications.
Webhook tests in the Webhook Dashboard will now trigger even if the underlying webhook is not enabled yet. With this change, your developers can easily validate that the webhook target app works as designed before enabling a webhook subscription.
With Web Proposal API, you can assure that your IT ecosystem (e.g., your CRM) has a valid link to the interactive proposal in Aurora. Your sales team, in turn, can share the publicly available Web Proposal link with the homeowner.
