Added new Cloud Connect API endpoints to support Terraform-based AWS onboarding and permission checks.

New endpoints:

• GET /core/v1/cloudconnect/supportedFeatures/{accountID}: Returns feature-level permission readiness for a connected account as: supportedFeatures[] with name and hasRequiredPermissions.
• POST /core/v1/cloudconnect/aws/accounts: Create or update an AWS account role.
• GET /core/v1/cloudconnect/aws/accounts/{accountID}: Get current account state.
• PUT /core/v1/cloudconnect/aws/accounts/{accountID}: Update AWS feature settings.
• DELETE /core/v1/cloudconnect/aws/accounts/{accountID}: Delete account role.

Response model additions:

• AwsAccountResponse (account info, role ARN, optional S3 config, supported features, linked time).
• SupportedFeaturesResponse / SupportedFeature for feature-permission status.

We updated the API contract for Cloud Diagrams to clarify error handling for statussheet ID routes.

For the affected endpoints, requests for unknown or inaccessible resource IDs now returns 403 Forbidden instead of 404 Not Found.

Actions to take:

• If your integration currently treats missing resources as 404, update it to also handle 403 for these Cloud Diagrams routes.

New Settings API with endpoints for managing Cloud Analytics custom report themes:

• GET /analytics/v1/settings/themes: Returns the list of custom color themes defined for your account.
• POST /analytics/v1/settings/themes: Creates a new custom color theme. Requires Cloud Analytics Admin permission.
• GET /analytics/v1/settings/themes/{id}: Returns a custom theme by the specified ID.
• PATCH /analytics/v1/settings/themes/{id}: Updates the custom theme specified by the Id. Requires Cloud Analytics Admin permission.
• DELETE /analytics/v1/settings/themes/{id}: Deletes the custom theme specified by the Id. Requires Cloud Analytics Admin permission.

Theme model

Each custom theme includes:

• name: Display name.
• primaryColor: HEX color (#RGB, #RRGGBB, or #RRGGBBAA).
• colors: Light and dark palettes, each with 1–32 hex colors.

Responses also return id, createTime, and updateTime.

Create requires name, primaryColor, and colors. Update accepts any subset of those fields.

Changes

New:

• POST /insights/v1/results/source/{sourceID}/insight/{insightKey}/resource-results: Replaces all resource results for the specified insight. Any existing unresolved resource results not present in the new set will be removed.

Changed:

• POST /insights/v1/results/source/{sourceID}/insight/{insightKey} now accepts metadata only. The resourceResults field was removed from the request body. Use the new resource-results POST above.
• status and dismissalDetails can be set on the same Insights POST request. Making a separate status call optional.
• GET Insights request responses now include dismissalDetails (dismissal reason and comment) for read-back and verification.
• Request/response schemas are split: writable request types are separate from response types, so server-computed fields (severity, resolved, enhancement, etc.) are not documented as client-writable.

Deprecated:

• PUT /insights/v1/results/source/{sourceID}/insight/{insightKey}/status: Still supported, but deprecated. Replaced by setting status and dismissalDetails on the POST calls.

Fixed:

• Resource result updates now persist result_type, location, resource_type, account, and provider.
• externalUrl prefers a user-provided URL and falls back to the auto-generated ARN URL when unset.
• Declarative resource-results writes no longer delete existing data if the upsert step fails.

Migration

If you send resourceResults on the single-insight POST, move that payload to POST /insights/v1/results/source/{sourceID}/insight/{insightKey}/resource-results.

GET /anomalies/v1 and GET /anomalies/v1/{id} now returns a notifications[] field on each anomaly.

The notifications[] field lists notification dispatch events in chronologically order. Each entry is a NotificationEvent with timestamp (dispatch time in UTC (RFC3339)) and channel (email, slack, or msteams) information.

Added four endpoints:

• GET /clouddiagrams/v1/statussheet/{id}/snapshots: Returns the list of saved snapshots for the specified diagram layer.
• GET /clouddiagrams/v1/statussheet/{id}/snapshot: Returns a single snapshot of the specified diagram layer identified by its ID.
• GET /clouddiagrams/v1/activity: Returns snapshot activity groups for the specified diagram layer, ordered by timestamp descending.
• GET /clouddiagrams/v1/activity/node-activities: Returns individual activity records for the specified component node, ordered by timestamp descending.

Added platform_info to the response body of the Get a support request endpoint.

The platform_info returns the cloud asset identifier the requester selected on the support form's asset-selector control, typically the GCP project ID, AWS account ID, Azure subscription ID, or equivalent.

Added Support API endpoints:

• POST https://api.doit.com/support/v1/tickets/{ticketId}/tags: Adds one or more tags to an existing support request. Existing tags are preserved.
• DELETE https://api.doit.com/support/v1/tickets/{ticketId}/tags: Removes one or more tags from an existing support request.

Added Cloud Analytics folder API with he following operations:

• GET https://api.doit.com/analytics/v1/folder: Returns Cloud Analytics folders the you have access to.
• POST https://api.doit.com/analytics/v1/folders: Creates a new Cloud Analytics folder.
• GET https://api.doit.com/analytics/v1/folders/{id}: Returns the specified Cloud Analytics folder.
• PATCH https://api.doit.com/analytics/v1/folders/{id}: Request body for updating folder properties. All fields are optional; only fields the caller wants to change are set.
• DELETE https://api.doit.com/analytics/v1/folders/{id}: Deletes the specified folder.

We are adding support for organizing reports and allocations into folders.

To support this we have added the ability to:

• Filter reports and allocations by folderId.
• Add a report or allocation to an existing folder by including folderId in a PATCH request. If folderId is omitted or empty, the item is placed in the root folder.

It is optional to use the folderId. Folders can be created and configured using the Folders API.