Rename a deploy hook

rename_deploy_hook

Changes the name of one deploy hook.

POST /v1/rename_deploy_hookScopeconfig:writeMakes changes

Only the label changes. The URL, whether it is on and its call log stay as they are, and the call log shows the new name from then on. See Deploy hooks.

Request

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

It makes changes, so send an Idempotency-Key header whenever you might retry it. A retry with the same key gets the first answer back instead of running again.

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

Over MCP, the same method is the rename_deploy_hook tool.

Inputs

Input	Type	Required	Description
`projectId`	string	Yes	The site id.
`hookId`	string	Yes	The hook id from `list_deploy_hooks`.
`name`	string	Yes	The new name. It cannot be empty, and it is cut to 64 characters.

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.