ReviseMy Try with your agent

Webhooks

Gate the pipeline when a human decides

Polling get_review works. For CI/CD and event-driven agents, pass an HTTPS webhook_url on create_review — ReviseMy POSTs a signed review.decided payload when you approve or request changes.

The problem

Agents that only poll burn cycles waiting on humans. Pipelines need a clear signal that the review was approved or sent back — without trusting an unsigned HTTP POST.

How ReviseMy fits

  1. 1

    create_review with an HTTPS webhook_url (and your usual source).

  2. 2

    You approve or request changes on the review (or inline MCP App).

  3. 3

    Your endpoint receives review.decided — check status and next_action, verify X-ReviseMy-Signature, then continue or stop the pipeline.

What gets delivered

Event: review.decided

Payload includes decided_at and the same agent-shaped review object get_review returns — status, next_action, work packets.

HMAC with the review token

Headers: X-ReviseMy-Event, X-ReviseMy-Review, X-ReviseMy-Signature: sha256=<hmac>. Key = owner token from review_url. Verify before trusting.

Queued retries

Delivery is queued (10s timeout, 3 attempts with backoff). Failures are logged and never block the human decision.

Inherits on parent_id passes

Follow-up create_review calls with parent_id keep the parent webhook so multi-pass loops stay wired.

Integration checklist

  • HTTPS webhook_url on create_review (http only in local/testing)
  • Verify HMAC-SHA256 of the raw body with the owner review token
  • Branch on review.status: approved vs changes_requested
  • Read review.next_action for what the agent should do next
  • Prefer webhooks for CI gates; poll get_review when you need mid-loop progress

FAQ

Do I still need to poll get_review?

For mid-loop work (wait_for_human, applying marks) polling or MCP Apps still help. Use the webhook when you care about the decision moment — especially CI approve/block.

What if delivery fails?

ReviseMy retries a few times with backoff, then logs the failure. The human decision already succeeded — your endpoint should be idempotent.

Where is the deep setup?

See /connectors for host setup and docs/CONNECTORS.md for the full webhook contract.

Try with your agent