Mint webhook ingress endpoints
const url = 'http://localhost:11044/api/v1/channels/credentials/example/ingress';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/credentials/example/ingress \ --header 'X-Embabel-Api-Key: <X-Embabel-Api-Key>'JSON fields: installationId, expectedRevision. The url of each webhook channel, with a new secret returned exactly once. Later calls give the url and a null secret: only the hash is kept.
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. Every webhook channel this realm declares gets an endpoint
Responses
Section titled “Responses”OK
Where one declared webhook channel takes deliveries; answered by POST /channels/credentials/{realmName}/ingress
object
Name of the webhook channel the realm declares
The installation this was read from
object
Digest of the realm snapshot the installation admitted, 64 lowercase hex characters
The live installation’s id; send it back as installationId on a change
Name of the installed realm
The installation’s revision; send it back as expectedRevision on a change. Every bind or revoke moves it
The delivery secret, returned only by the call that minted the endpoint; null on every later call, since only its hash is kept
The address to paste into the provider. Absolute when the host is configured with its public origin (assistant.channels.ingress-base-url), otherwise site-relative

