---
title: "Mark features as stale / not stale"
method: POST
path: "/api/admin/projects/{projectId}/stale"
tags: ["Features"]
---

# Mark features as stale / not stale

`POST /api/admin/projects/{projectId}/stale`

This endpoint marks the provided list of features as either [stale](https://docs.getunleash.io/concepts/technical-debt#stale-and-potentially-stale-flags) or not stale depending on the request body you send. Any provided features that don't exist are ignored.

## Path parameters

- `projectId` string, required

## Request body

- BatchStaleSchema — A list of features to operate on and whether they should be marked as stale or as not stale.
  - `features` string[], required — A list of features to mark as (not) stale
  - `stale` boolean, required — Whether the list of features should be marked as stale or not stale. If `true`, the features will be marked as stale. If `false`, the features will be marked as not stale.

## Response `202`

This response has no body.

## Other responses

- `401` — Authorization information is missing or invalid. Provide a valid API token as the `authorization` header, e.g. `authorization:*.*.my-admin-token`.
- `403` — The provided user credentials are valid, but the user does not have the necessary permissions to perform this operation
- `415` — The operation does not support request payloads of the provided type. Please ensure that you're using one of the listed payload types and that you have specified the right content type in the "content-type" header.

---

[API](https://skmtc.net/unleash/apis/unleash-api-3.md) · [All operations](https://skmtc.net/unleash/apis/unleash-api-3/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/unleash/unleash-api-3/revisions/b2c3116e633e/schema)