Delete Entity

Deletes an Entity model from the project’s schema, together with every content entry of that type.

Caution

This endpoint requires a Write Token in the Authorization header. Calling it with a regular (read) token returns 403 Forbidden.

Danger

This operation is irreversible and cascades: deleting a model deletes all of its content. The REST endpoint applies the deletion immediately — there is no dry-run or confirm flag at this layer. If you want a preview (“how many contents would this remove?”) before deleting, use the delete-content-island-model MCP tool, which gates the deletion behind a dry-run / confirm step.

Reference protection

If the model is referenced by a relation field on another model, the deletion is rejected with 409 CONFLICT and nothing is deleted. There is no force override — remove or repoint the referencing field first, then retry.

Tip

If you’re using JavaScript or TypeScript, the Content Island API client wraps this endpoint as client.deleteModel(...).

Endpoint

shell

curl -X DELETE https://api.contentisland.net/api/1.0/model/entity/:id \
--header 'Authorization: Bearer YOUR_WRITE_TOKEN'

Path Parameters

Name	Type	Required	Description
id	string	yes	The 24-character id of the entity to delete.

Example

shell

curl -X DELETE https://api.contentisland.net/api/1.0/model/entity/660f5b8a3a1c2d4e7f8b9012 \
--header 'Authorization: Bearer YOUR_WRITE_TOKEN'

Response

On success the endpoint returns 204 No Content with an empty body.

Status Codes

Code	Description
204	The model and its content were deleted.
401	Unauthorized. The token is missing, malformed or expired.
403	Forbidden. The token does not have write permissions — use a Write Token.
404	No entity with the given :id exists in the project.
409	The model is referenced by a field on another model and cannot be deleted. Remove the reference first.
500	Internal server error.