With webhook filters, you have fine control over which events in your Aurora tenant to notify your applications. The filters are a list of webhook URL attributes and their values that would cause webhooks to fire. You can apply filters to one or more URL attributes of any webhook event. For example, adding "filters": {"<STATUS>": ["sold", "plant_set_completed"]} to a project_status_changedwebhook subscription would cause the webhooks to fire only after the project status changes to one of the two values.
You can now configure single sign-on (SSO) access for your Aurora users via an API. The SSO access enables your team members to log in to Aurora with the same credentials they use in the rest of your IT ecosystem. With the new SSO Provider API endpoints, you can self-configure your Aurora tenant to use an identity provider that supports the OpenID Connect protocol (e.g. Salesforce, Okta, Duo Security). For detailed instructions, check out the Configure Single Sign-On tutorial.
You can now specify a minimum Total Solar Resource Fraction (TSRF) or Solar Access Percentage (SAP) in Energy Mode (previously this parameter was available in Max Fit only). If the TSRF or SAP of a given panel location is below the threshold, no panel will be placed.
You can now trigger project_created webhooks when a new project is created in Aurora. The webhook payload includes <SOURCE>, enabling you to determine if the project was created from the Aurora app or an API. With the new webhook event, you can be assured that your IT ecosystem always has complete and up-to-date project information regardless of how the project was created in Aurora.
The Retrieve Lead API now includes three new fields intended to make it easier to track the source of incoming leads. The new fields are marketing URL parameters from Lead Capture AI leads (referrer_params) plus identifying information for the Lead Capture template (template_id and template_name).
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_created, lead_changed, and lead_converted. With [the new APIs] (ref:retrievelead) 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).
