---
title: "PUT /boards/{board_uuid}/statuses/{status_uuid}/entry-requirements"
method: PUT
path: "/boards/{board_uuid}/statuses/{status_uuid}/entry-requirements"
tags: ["Boards"]
---

# PUT /boards/{board_uuid}/statuses/{status_uuid}/entry-requirements

`PUT /boards/{board_uuid}/statuses/{status_uuid}/entry-requirements`

## Request

- Base URL: `https://api.laver.app` (the document declares no server; this is the origin it was published from)
- URL: `https://api.laver.app/boards/{board_uuid}/statuses/{status_uuid}/entry-requirements`
- Auth: one of:
  - HTTP bearer
  - API key in header `Authorization`

## Path parameters

- `board_uuid` string, uuid, required
- `status_uuid` string, uuid, required

## Request body

- object
  - `entry_requirements` object[], required
    - `type` union, required
      - 'has_attachment'
      - 'custom_field_filled'
      - 'has_assignee'
      - 'has_due_date'
      - 'subtasks_done'
      - 'has_subtasks'
      - 'not_blocked'
    - `custom_field_uuid` string, uuid, nullable

## Response `2XX`

Success. This endpoint declares no response schema, so its body is not part of the generated contract.

## Other responses

- `400`: The request failed schema validation, or the handler rejected its contents. Undeclared properties are rejected on every body, path and query schema, so an unexpected field is a 400 rather than a silently ignored one.
- `401`: No credential, or one that is expired, revoked or not accepted by this endpoint.
- `402`: The request would exceed a plan limit, or the workspace has been made read-only over an unpaid invoice. Billing never refuses a read: a workspace in any billing state can still be read in full and exported, and only its writes are turned away.
- `403`: Authenticated, but not allowed: a `viewer` attempting a write, a `commenter` attempting any write other than a comment on a ticket it can see, a `guest` writing anywhere or a `guest_editor` writing outside the boards it was given, a non-admin on an admin route, a non-owner on billing, or a non-staff user on staff tooling.
- `404`: No such resource — or one the caller may not see. Membership and board access are enforced by answering 404 rather than 403, so a stranger never learns that a resource exists.
- `423`: The workspace is suspended, which is an action taken by Laver rather than a billing state. Reads are refused alongside writes, and no plan change lifts it — unlike a 402, which the workspace can settle itself.
- `429`: The rate limit was exceeded. The budget is keyed on the authenticated session user or API key, falling back to the caller IP.

---

[API](https://skmtc.dev/laver/apis/laver-api.md) · [All operations](https://skmtc.dev/laver/apis/laver-api/llms.txt) · [OpenAPI document](https://skmtc.dev/laver/apis/laver-api/revisions/91e3db25a19c?raw)