jobhunt.app/mcp

Work with webhook events

Connect a reviewed destination and inspect delivery evidence.

Updated

Step by step

  1. Review the destination and events

    Use the subscription creation review and explicit consent flow. Configuration needs webhook authority and the source-data grants required for the selected events.

  2. Retain signing material privately

    Follow the recipient-encrypted delivery contract. Keep decryption local, verify private retention, then acknowledge delivery.

  3. Inspect attempts before retrying

    Use delivery and job reads for factual status. A missing receiver reply does not prove the receiver rejected the event.

What happens next

Webhook configuration, signing delivery and asynchronous delivery remain separate recorded operations.

Troubleshooting

Test and retry actions can contact the configured destination. A status read or bookkeeping reconciliation does not itself authorize another send.

Technical detailsAPI operations and permissions

These operation details and permissions come from the API contract.

READlist_webhook_subscriptions

Read every owned nonfinancial webhook subscription in stable ID pages of 25, including inactive subscriptions. Directory omits URL/events; get the complete native metadata or its checksummed file. No signing secret. Reads create nothing and require the captured account.

GET /api/v1/journey/list_webhook_subscriptions

DECLARED PERMISSIONS

  • read:webhooks
View input, output and access requirements →
READlist_webhook_deliveries

Read native delivery-attempt history for one owned webhook in stable ID pages of 25. Failed and successful attempts remain distinct from queued worker jobs; directory omits error details; get complete native attempt metadata or its checksummed file. No payload, response body or signing secret.

GET /api/v1/journey/list_webhook_deliveries

DECLARED PERMISSIONS

  • read:webhooks
View input, output and access requirements →
READlist_webhook_delivery_jobs

List the delivery jobs of one webhook subscription in pages of 25. Review and explicitly queue one synthetic webhook.test using the saved destination and signing service, or inspect owned existing durable delivery facts and reconcile only a matching committed HTTP2xx receipt. Exact account/source/actor review, true consent, shared receipts and deterministic receiver key; no automatic new request. No arbitrary payload, signing key, private event/response body or synchronous external IO. Paused subscriptions may receive an explicitly authorized synthetic test, preserving native test behavior; ordinary events remain paused. Reconciliation never sends or changes receiver receipts. Unconfirmed/failed/legacy outcomes stay factual and require separate review.

GET /api/v1/journey/list_webhook_delivery_jobs

DECLARED PERMISSIONS

  • read:webhooks
View input, output and access requirements →