floor-blocks

Remove Block

Remove a block nobody has accepted (a draft or an offered block), and keep the scheduler from posting it again for that window.

Frederick, 2026-10-09, on the Saturday 4-8 PM block of the week of 2026-10-12: "2 should be enough, 2 sort and scan, one print, 1-2 packing and shipping" and "for the packaging and shipping we can add blocks if we need to". The whole rule, and what it deliberately does not do, is in app.modules.floor_blocks.removal; how the engine and the daily pattern read the removal is app.modules.floor_blocks.manager_holds. This route maps the typed refusals: 404 no such block, 409 somebody has the block ("Someone has this block. Move it or talk to them.") or it is in a state a removal does not apply to, 422 a reason shorter than MIN_REMOVAL_REASON_CHARS.

GATED hr:contractors:write, the grant move_block and the other manager floor actions use, so no grant was invented. A caller without it gets the platform's 403 before anything is read.

post/api/floor/blocks/{block_id}/remove

Request

  • Base URL: https://api.pigeonly.com (the document declares no server; this is the origin it was published from)
  • URL: https://api.pigeonly.com/api/floor/blocks/{block_id}/remove
  • Auth: none declared

Path parameters

block_idstring uuid required

Request body

reasonstring required

Response

Successful Response

object required

Changes

No recorded changes to this operation across all 1 revision of this API.