# Card not found

> Canonical HTML: https://screenrig.ai/problems/card-not-found/

HTTP 404 · `card_not_found`

## What it means

The API answers with HTTP 404 Not Found and an `application/problem+json` document when the condition is Card not found. The document's `type` member is `https://screenrig.ai/problems/card-not-found`, the address of this page, and its `code` member is `card_not_found`.

## What to do

Read GET /api/cards for project card instances or GET /api/card-types for catalogue types. Address instances by their global UID and write dynamic properties at /api/cards/{id}/data.

## Player action

This problem defines no Player action class. It belongs to a project, pairing or account flow that an agent or the dashboard drives.

## Reference

| Field | Value |
| --- | --- |
| Code | `card_not_found` |
| HTTP status | `404 Not Found` |
| Type | `https://screenrig.ai/problems/card-not-found` |
| Player action | `none` |

- [All problem types](https://screenrig.ai/problems/)
- [API reference](https://screenrig.ai/docs/api/#problems)
- [Problem registry YAML](https://screenrig.ai/docs/api/problems.yaml)