Eliminar una funcion de webhook
Functions
DELETE /v1/functions/{id}
Delete a webhook function permanently. Fails while any block still references it.
DELETE
Eliminar una funcion de webhook
Deletes the function. This is a hard delete and it cannot be undone.
It is refused while any block still references the function, and the error names them — so the normal sequence is: read
used_by_blocks, unbind those blocks in the portal, then delete.
Endpoint
Required scope
assistants:write
Headers
Path parameters
Example request
Response
204 No Content
Deleted. No body.401 Unauthorized
Missing, invalid, revoked, or expired token.403 Forbidden
The token does not have theassistants:write scope.
404 Not Found
No webhook function with that id in the token’s company. A repeated delete lands here, so treat404 as “already gone”.
409 Conflict
error.code is AGENT_TOOL_IN_USE. At least one block still references the function; error.details.blocks lists them.
502 Bad Gateway
The assistant service is unreachable.Operational notes
- The
409is the useful part of this endpoint. It is what stops you silently breaking an assistant mid-conversation, and it tells you exactly which blocks to fix. - Unbinding a function from a block is done in the portal. This API can save a block’s text but not its function bindings, so the last step of a clean removal is a portal action.
- Deleting is company-wide. A function used by an assistant in another project of the same company counts as in use and blocks the delete.
- A retry is safe: the second call is a
404, never a partial delete. is_active: falseis the reversible alternative and is usually what you want when retiring an integration gradually.