Skip to main content
DELETE
Revoke a registered extension

Authorizations

Authorization
string
header
required

Enforced on every transport, with no exempt operation. A person's request — over the default local unix socket exactly as over a TCP listener — must carry a JWT issued by the configured identity provider, which the host verifies itself against that issuer's key set: signature, issuer, expiry, and the person and organisation it names. Requests without a valid one receive 401 NRY-0011. The socket's file permissions are transport and are not an authorisation.

Path Parameters

publisher
string
required

The publisher half of the extension's namespaced name.

The name is publisher/extension and travels as TWO path segments rather than one. The single-segment spelling is not broken — a generated client percent-encodes a path parameter's slash and the router decodes it back — so this is a deployment choice rather than a repair: an encoded slash is normalised or rejected by most reverse proxies a hosted home sits behind, and two segments read the way the name reads, /v1/extensions/lerian/redactor.

Pattern: ^[a-z0-9][a-z0-9-]*$
Example:

"lerian"

name
string
required

The extension half of the namespaced name.

Pattern: ^[a-z0-9][a-z0-9-]*$
Example:

"redactor"

Response

The registration is gone.