Revoke a channel's handshake
const url = 'http://localhost:11044/api/v1/channels/captured/example/example/handshake/revoke';const options = {method: 'POST', headers: {'X-Embabel-Api-Key': '<X-Embabel-Api-Key>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url http://localhost:11044/api/v1/channels/captured/example/example/handshake/revoke \ --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'JSON fields: installationId, expectedRevision.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”Name of the captured realm installed in the signed-in owner’s world; non-blank, at most 256 UTF-8 bytes, no control characters and not all * (400 otherwise). 409 when its live installation is not the one named by the body’s installationId and expectedRevision
Channel the realm declares, by the name the channel list gives; same text rules as the realm name. 404 when undeclared, 400 when the channel declares no handshake or no dial credential, or its handshake operation is undeclared, outside the egress policy, or its credential is unbound; 409 when its handshake is not approved
Responses
Section titled “Responses”OK
Where one channel’s pre-connect handshake approval stands after POST …/handshake/grant or …/handshake/revoke on /channels/captured/{realmName}/{channelName}
object
True when the handshake is now approved to run its declared operation under the channel’s own credential; false when the approval was revoked
Name of the channel, as the realm declares it
The realm installation the approval was recorded on
Name of the captured realm the channel belongs to
The installation’s revision after the change: what the next start, stop or handshake decision must send back as expectedRevision

