Deliver a webhook
Continues every session waiting on key (the wait_for tool) and starts every flow with on: { hook: key }, with the body as the next message. No token: the body is signed with the server's hookSecret. GitHub's x-hub-signature-256 and x-github-delivery work as they are.
key*stringWhat the sessions wait on
x-pistis-signature*stringsha256= and the hex HMAC-SHA256 of the raw body with the secret
x-pistis-delivery*stringUnique per event: a repeat is duplicate and does nothing
body*unknownapplication/jsonDelivered, or a repeat
application/json- response
status*unknownsessions*integerHow many sessions continue
curl -X POST 'http://127.0.0.1:7777/hooks/ci-1234' \ -H 'x-pistis-signature: sha256=0000' \ -H 'x-pistis-delivery: d-1' \ -H 'Content-Type: application/json' \ -d '{ "status": "green"}'{ "status": "delivered", "sessions": 0}Revoke an access or refresh token (RFC 7009) POST
Always 200. A refresh token takes its whole family with it.
Deliver a code host's webhook POST
Pull request feedback: a review comment, a review that requests changes, a comment that mentions `@pistis`, or a failing check on a pull request a session opened becomes a message in that session, as the person who wrote it and only if they may message it. Point the code host's webhook here (GitHub: the App's webhook URL) with the connection's webhook secret; the code host signs every delivery. Anything not acted on is recorded with why.