Not all Aurora API features are available to all customers by default. Some require a specific plan tier; others are add-ons that must be explicitly provisioned for your tenant. This page describes which features have availability requirements and what to expect when a feature is not accessible.
Plan tiers
Aurora offers multiple plan tiers; not all tiers include API access. Of those that do, Build, Grow, and Scale are the main API-accessible tiers. All three include the Sync API (projects, designs, proposals, agreements, orders, and related resources). The Design API and certain add-on features are available only on specific tiers or with explicit provisioning.
Your plan tier and provisioned add-ons are determined by your Aurora contract. Contact your Aurora account manager for details.
Feature availability matrix
Core workflow features
| Feature | Availability |
|---|---|
| Sync API | All API-enabled tiers |
| Design API (AutoDesigner, Irradiance Analysis, Performance Simulation, Fire Pathway Placement) | Add-on to Business Plans |
| Aurora AI (AI Roof) | Add-on; included in Scale tier |
| Contract Manager | Add-on; included in Scale tier |
| Expert Design — Site Modeling Service | Add-on (per-use, consumes credits) |
| Expert Design — EagleView | Add-on (per-use, consumes credits) |
| Plan Sets | Add-on (per-use, consumes credits) |
Platform and account features
These features are not part of the core design and sales workflow but may be relevant to larger deployments.
| Feature | Availability |
|---|---|
| Single Sign-On | Grow and Scale tiers |
| Partner Management | Grow and Scale tiers |
| Advanced Roles | Grow and Scale tiers |
| Teams | Grow and Scale tiers |
Provisioning-gated endpoints
The following endpoints require the corresponding feature to be explicitly provisioned for your tenant. Calling them without provisioning returns a 422 Unprocessable Entity response with an error message indicating the feature is not available.
- AutoDesigner —
POST /tenants/{tenant_id}/designs/{design_id}/auto_designer/run - Irradiance Analysis —
POST /tenants/{tenant_id}/designs/{design_id}/irradiance_analysis/run - Performance Simulation —
POST /tenants/{tenant_id}/designs/{design_id}/performance_simulation/run - Fire Pathway Placement —
POST /tenants/{tenant_id}/designs/{design_id}/fire_pathway_placement/run - AI Roof —
POST /tenants/{tenant_id}/designs/{design_id}/ai_roof/run— part of the Sync API; access is determined by plan add-on or Scale tier inclusion rather than a separate provisioning gate. Credits are charged per accepted run.
If you receive an unexpected422on one of these endpoints and your inputs are well-formed, the most likely cause is that the feature has not been provisioned for your tenant. Contact [email protected] to confirm your tenant's provisioning.
Distinguishing provisioning errors from other errors
A 422 Unprocessable Entity can occur for two distinct reasons:
- Input validation failure — one or more request parameters are missing or malformed. The response body will describe the specific field or condition.
- Feature not provisioned — the tenant does not have access to the requested operation. The response body will indicate that the feature is unavailable.
In both cases, the response body contains a message field with a human-readable explanation. Agents and integrations should read this message before retrying or escalating.
For a full list of HTTP response codes and error formats, see HTTP Response Codes.