Blocks
Delete a block
Move a block to the trash. It can be restored for 30 days. Requires Update content.
DELETE
Moves a block and its children to the trash. Requires Update content. You can restore it for 30 days.
string
Optional. Only
2026-03-11 is accepted. Without it, the current version is used. A different value returns 400.string
required
A block ID. A subpage, row, or database ID moves that subpage, row, or database to the trash.
What moves with it
- Subpages and inline databases inside the block move to the trash too. They come back when you restore the block.
- A subpage or inline database that was deleted before this block stays deleted.
- If the block holds a subpage or database the integration can’t write, the whole request returns 403 and nothing changes.
Read a deleted block
These rules cover blocks deleted through this API,
in_trash: true, Markdown edits, and erase_content. A block a person deleted in the app returns 404 and can’t be restored through the API.
Restore
- A restored block goes to the end of its parent. If the parent no longer exists, it goes to the end of the document.
- A block whose parent is also deleted can’t be restored on its own. The response is 400.
- A subpage or database inside a deleted block can’t be restored on its own either. Restore the block.
- If deleting one column left a single column, that list was removed. Restoring the column puts its blocks at the end of the document, and the response is the first of them.
Response
The block object within_trash: true. See Retrieve a block.
Errors
See Common rules for shared errors.