Verification history (read-only)

Developing

GET

/ui-extensions/registry/{id}/versions

Last modified:2026-08-19 13:49:58

OperationId:listUiExtensionVersions

Every submitted version with its verdict and full analysis report (admin detail: reports name a partner's source files and lines). The active one is marked. Submission is NOT here — POST …/deploy is the write.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

Authorization: Bearer ********************

Path Params

Responses

🟢200OK

application/json

Version history, newest first. This is where is_active — the per-version "currently live" state — is read. There is no promoted here: that is a deploy outcome, not a property of a version row.

Bodyapplication/json

🟠401Unauthorized

🟠403Forbidden

🟠404Record Not Found

Request Example

Shell

JavaScript

Java

Swift

curl --location 'https://awqacore01.crexendocloud.com/ns-api/v2/ui-extensions/registry//versions' \
--header 'Authorization: Bearer <token>'

Response Example

200 - Example 1

{
    "versions": [
        {
            "version_id": "string",
            "version": "1.0.4",
            "status": "approved",
            "is_active": true,
            "has_chunk_sri": "yes",
            "integrity_hash": "string",
            "verified_at": "2019-08-24T14:15:22.123Z",
            "ruleset_fingerprint": "string",
            "report": {
                "property1": "string",
                "property2": "string"
            }
        }
    ]
}

Modified at 2026-08-19 13:49:58

Delete an access rule

Read platform-global SDK settings