# Card data document does not fit a card that reads it

> Canonical HTML: https://screenrig.ai/problems/card-data-invalid/

HTTP 409 · `card_data_invalid`

## What it means

The API answers with HTTP 409 Conflict and an `application/problem+json` document when the condition is Card data document does not fit a card that reads it. The document's `type` member is `https://screenrig.ai/problems/card-data-invalid`, the address of this page, and its `code` member is `card_data_invalid`.

## What to do

A card placement reads this card data key and refuses the document: errors[0].card names that card and errors[0].field the failing property. Correct the document to hold only that card's dynamic properties, valid against its schema, then write it again or republish.

## 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_data_invalid` |
| HTTP status | `409 Conflict` |
| Type | `https://screenrig.ai/problems/card-data-invalid` |
| 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)