---
title: "Delete a field"
method: DELETE
path: "/api/board/{boardId}/configuration/fields/{fieldUuid}"
tags: ["Board"]
---

# Delete a field

`DELETE /api/board/{boardId}/configuration/fields/{fieldUuid}`

## Request

- Base URL: `https://core-api.getaptly.com`
- URL: `https://core-api.getaptly.com/api/board/{boardId}/configuration/fields/{fieldUuid}`
- Auth: one of:
  - API key in header `x-token`
  - HTTP bearer
- TypeScript: <https://skmtc.dev/getaptly/apis/aptly-api/docs/api/board/:boardId/configuration/fields/:fieldUuid/delete.ts> (a function with typed inputs; its response is checked against the schema)

Removes a field from the board (card values already stored for it are left in place). Refused
for standard fields (`name`, `stage`, `description`, `tags`, `checklist`, `files`,
`lastAction`, `dueAt`, `relatedContacts`), locked, mirror and integration-managed fields (403),
and - as in the Aptly app - for a field used by a saved filter, or by a workflow or automation
that runs off one (409 `CONFLICT`, with the dependents in `meta`). Requires `update` permission
and "Edit Boards" access (not needed on a board that same key created).

## Path parameters

- `boardId` string, required
- `fieldUuid` string, required

## Response `200`

Field deleted.

- object
  - `data` object
    - `uuid` string
    - `deleted` boolean

## Other responses

- `401`: Invalid or missing API key.
- `403`: Missing permission or "Edit Boards" access, or the field can't be deleted.
- `404`: Board or field not found.
- `409`: The field is used by saved filters, workflows or automations.

---

[API](https://skmtc.dev/getaptly/apis/aptly-api.md) - [All operations](https://skmtc.dev/getaptly/apis/aptly-api/llms.txt) - [OpenAPI document](https://skmtc.dev/getaptly/apis/aptly-api/revisions/75c367e0b8e5?raw)