Remove one call from the log
delete_deploy_hook_call
Hides one call from a site's deploy hook call log and from the counts.
The call stops appearing in list_deploy_hook_calls and in the counts of list_deploy_hooks and get_deploy_hook_call_stats. A logged call holds the caller's IP address and user agent, so reach for this when somebody does not want one kept.
The row is flagged rather than erased and leaves the database 30 days after it is hidden, or at once when its hook is deleted. It changes the record only, so a build the call started is not affected. See Deploy hooks.
Request
Call it with a POST to https://api.modulify.ai/v1/delete_deploy_hook_call, sending the inputs below as a JSON object. The token needs the config:write scope.
This method is marked destructive: it deletes or overwrites data. Check the inputs before you call it, and send an Idempotency-Key header whenever you might retry it.
curl -X POST https://api.modulify.ai/v1/delete_deploy_hook_call \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"projectId":"PROJECT_ID","callId":"CALL_ID"}'Over MCP, the same method is the delete_deploy_hook_call tool.
Inputs
| Input | Type | Required | Description |
|---|---|---|---|
projectId |
string | Yes | The site id. |
callId |
string | Yes | The call id from list_deploy_hook_calls. |
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.