Update an access rule

Developing

PUT

/ui-extensions/registry/{id}/access/{rule_id}

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

OperationId:updateUiExtensionAccessRule

Edits a rule IN PLACE by its handle — scope fields included, so moving a rule to another domain is one call. PER-FIELD: a field absent from the body keeps its stored value (an enabled-only edit cannot move the rule to the wildcard scope). Moving onto another rule's tuple is a 409 against that rule; a reseller can neither move a rule out of their scope nor into another's.

Request

Authorization

Bearer Token

Provide your bearer token in the

Authorization

header when making requests to protected resources.

Example:

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

Path Params

Body Params application/jsonRequired

Examples

Responses

🟢202Accepted

application/json

Accepted — the write is published to the cluster and lands asynchronously. The body is the uniform acknowledgement envelope — {code, message}, plus warnings when the write raised any. No identifier is returned: writes are keyed on what the caller named.

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Record Not Found

🟠409

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PUT 'https://awqacore01.crexendocloud.com/ns-api/v2/ui-extensions/registry//access/' \
--header 'Authorization: Bearer <token>' \
--header 'Content-Type: application/json' \
--data '{
    "extension_id": "string",
    "hostname": "*",
    "reseller": "*",
    "domain": "*",
    "role": "*",
    "enabled": "yes"
}'

Response Example

202 - Example 1

{
    "code": 0,
    "message": "string"
}

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

Create an access rule

Delete an access rule