---
title: "Get project status"
method: GET
path: "/api/admin/projects/{projectId}/status"
tags: ["Projects"]
---

# Get project status

`GET /api/admin/projects/{projectId}/status`

This endpoint returns information on the status the project, including activities, health, resources, and aggregated flag lifecycle data.

## Path parameters

- `projectId` string, required

## Response `200`

projectStatusSchema

- ProjectStatusSchema — Schema representing the overall status of a project, including an array of activity records. Each record in the activity array contains a date and a count, providing a snapshot of the project’s activity level over time.
  - `activityCountByDate` object[], required — An array of project activity information. Each item contains a date and the total number of activities for that date.
    - `date` string, required — Activity date
    - `count` integer, required — Activity count
  - `health` object, required — Information about the project's health rating
    - `current` integer, required — The project's current health score, based on the ratio of healthy flags to stale and potentially stale flags.
  - `technicalDebt` object, required — Information about the project's health rating
    - `current` integer, required — The project's current health score, based on the ratio of healthy flags to stale and potentially stale flags.
  - `resources` object, required — Key resources within the project
    - `apiTokens` integer, required — The number of API tokens created specifically for this project.
    - `members` integer, required — The number of users who have been granted roles in this project. Does not include users who have access via groups.
    - `segments` integer, required — The number of segments that are scoped to this project.
  - `staleFlags` object, required — Information on stale and potentially stale flags in this project.
    - `total` integer, required — The total number of flags in this project that are stale or potentially stale.
  - `lifecycleSummary` object, required — Feature flag lifecycle statistics for this project.
    - `initial` object, required — Statistics on feature flags in a given stage in this project.
      - `averageDays` number, nullable, required — The average number of days a feature flag remains in a stage in this project. Will be null if Unleash doesn't have any data for this stage yet.
      - `currentFlags` integer, required — The number of feature flags currently in a stage in this project.
    - `preLive` object, required — Statistics on feature flags in a given stage in this project.
      - `averageDays` number, nullable, required — The average number of days a feature flag remains in a stage in this project. Will be null if Unleash doesn't have any data for this stage yet.
      - `currentFlags` integer, required — The number of feature flags currently in a stage in this project.
    - `live` object, required — Statistics on feature flags in a given stage in this project.
      - `averageDays` number, nullable, required — The average number of days a feature flag remains in a stage in this project. Will be null if Unleash doesn't have any data for this stage yet.
      - `currentFlags` integer, required — The number of feature flags currently in a stage in this project.
    - `completed` object, required — Statistics on feature flags in a given stage in this project.
      - `averageDays` number, nullable, required — The average number of days a feature flag remains in a stage in this project. Will be null if Unleash doesn't have any data for this stage yet.
      - `currentFlags` integer, required — The number of feature flags currently in a stage in this project.
    - `archived` object, required — Information on archived flags in this project.
      - `currentFlags` integer, required — The number of archived feature flags in this project. If a flag is deleted permanently, it will no longer be counted as part of this statistic.
      - `last30Days` integer, required — The number of flags in this project that have been changed over the last 30 days.

## 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
- `404` — The requested resource was not found.

---

[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/versions/b2c3116e633e/schema)