Revoke a captured source
const url = 'http://localhost:11044/api/v1/channels/sources/example/example/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/sources/example/example/revoke \ --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'JSON fields: installationId, expectedRevision. Publishing and delivery on the source stop.
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
Approved source to revoke; same text rules as the realm name. 400 when the admitted capture does not declare it, 409 when it is not approved
Responses
Section titled “Responses”OK
One event source a captured realm declares, and whether the owner approved it; answered by the /channels/sources/{realmName} list, grant and revoke routes
object
Digest of the realm snapshot the installation admitted, 64 lowercase hex characters
The live installation of that realm this was read from; send it back as installationId on a change
Name of the source: the stem of its sources/
Name of the realm that declares the source
That installation’s revision; send it back as expectedRevision on a change
Revision of the source’s approval, which moves independently of the installation’s revision and is what a consumer grant names as sourceRevision; null while the source is not approved
Journal stream the source’s events are appended to; the same as name
Event type, the source name qualified by its realm:

