export_site_webhooks

Each webhook comes back under Webhooks with its name, destination host, payload type, the events it listens to, whether it is enabled and when it was created, and ExportedAt says when the export was made. This is the tool for showing somebody their whole webhook setup at once.

Signing secrets are never included, and the destination comes back as Host only, exactly as list_site_webhooks reports it, because a full webhook URL is itself a credential. That means an export cannot be replayed onto another site without you supplying the URLs again. See Webhooks.

Request

Call it with a POST to https://api.modulify.ai/v1/export_site_webhooks, sending the inputs below as a JSON object. The token needs the config:read scope.

It only reads and changes nothing, so retrying it is safe.

curl -X POST https://api.modulify.ai/v1/export_site_webhooks \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"projectId":"PROJECT_ID"}'

Over MCP, the same method is the export_site_webhooks tool.

Inputs

Response

Every call answers with the JSON envelope of success, message, data, code and version. data holds the result described above, and on a method that returns a total, count carries it. The response headers carry the call's X-Request-Id and what is left of your per-minute budget in X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset. Errors explains every status code a call can answer with.