Skip to main content
DELETE
Revocation is:
  • Immediate. The widget key fails authentication on the very next widget request, so the widget stops working on every page that embeds it. There is no cache to wait out.
  • Terminal. A revoked deployment cannot be reactivated. To embed again, create a new deployment and update your page with its new key.
  • Idempotent. Revoking a deployment that is already revoked succeeds and returns it unchanged, with its original revoked_at.
The response is 200 with the revoked deployment, so you can read revoked_at without a second request. The deployment stays in List widget deployments with status set to revoked. A deployment that does not exist, a deployment in another organization and a malformed ID all return the same 404. You need the assistant.publish permission, which the owner, admin and editor roles hold. Authenticate with an arukz_sk_ API key or a signed-in console session.
string
required
The deployment’s ID (UUID), as returned in id.

Response

string
required
The deployment’s ID (UUID).
string
required
The embed’s label.
string
required
The widget key, which no longer authenticates.
string
required
The embedded assistant’s ID.
string
required
Always revoked.
string[]
required
The origin list as it was at revocation.
string
required
When the deployment was created, ISO 8601 in UTC.
string | null
required
ID of the user who created it, or null when it was created with an API key.
string | null
required
When the embed would have expired, or null.
string
required
When the embed was revoked, ISO 8601 in UTC.
string | null
required
When the widget key last authenticated a request, or null if never.
Last modified on September 26, 2026