# Daily specials card

> Canonical HTML: https://screenrig.ai/docs/cards/daily-specials/

Show today's featured dish and price, with the whole week alongside.

Give today's dish the spotlight and keep the week easy to browse. Dated exceptions replace the regular dish without changing the weekly menu.

## Live card

This card is drawn in your browser by the same code the Players run, with sample data.

Category: Food and drink. Tags: Restaurants and cafes, Prices and rates, Schedules.

## Layouts

This fullscreen card fills the whole screen in landscape or portrait and is not placed as a corner, chip, or strip.

Layouts: full. Forms: landscape, portrait.

[Card layouts, themes and publishing](/docs/cards/). [Browse the cards](/apps/#cards).

## Data and privacy

This card uses its configured properties and live card data.

## Properties

For theme, background, accent and position, see [Common properties](/docs/cards/#common-properties).

Set static properties in `params`. Bind `data` to a project card data key for live values; that document holds only dynamic properties. Without a data key, put the complete configuration in `params`. Nested rows describe the contents of their parent property.

### Static properties

| Name | Type | Default | Values and limits | Description |
| --- | --- | --- | --- | --- |
| `title` | string | `"Daily specials"` | maxLength: `60` |  |
| `closedMessage` | string | `"Explore the week’s specials below."` | maxLength: `160` |  |

### Dynamic properties

| Name | Type | Default | Values and limits | Description |
| --- | --- | --- | --- | --- |
| `footnote` | string | `""` | maxLength: `160` |  |
| `updatedAt` | string | `""` | maxLength: `40` | ISO instant for a synchronized menu update. The new local day is also a synchronized moment. |
| `specials` | array | `[]` | minItems: `0`; maxItems: `14` | ISO weekdays 1 Monday through 7 Sunday. The last entry for a repeated day wins. |
| `specials[].day` | integer |  | minimum: `1`; maximum: `7`; Required |  |
| `specials[].name` | string |  | minLength: `1`; maxLength: `80`; Required |  |
| `specials[].description` | string | `""` | maxLength: `240` |  |
| `specials[].price` | string | `""` | maxLength: `30` |  |
| `exceptions` | array | `[]` | minItems: `0`; maxItems: `32` | Dated replacements or days without a special. The last matching date wins. |
| `exceptions[].date` | string |  | pattern: `"^\\d{4}-\\d{2}-\\d{2}$"`; Required |  |
| `exceptions[].closed` | boolean | `false` |  |  |
| `exceptions[].name` | string | `"Special of the day"` | maxLength: `80` |  |
| `exceptions[].description` | string | `""` | maxLength: `240` |  |
| `exceptions[].price` | string | `""` | maxLength: `30` |  |

## Canvas example

Add this item to a playlist page’s `primitives`. [Publish the playlist and assign a screen](/docs/cards/#publish-a-card-canvas).

```json
{
  "id": "daily-specials",
  "primitive": "card",
  "card": "daily-specials",
  "major": 1,
  "params": {
    "theme": "neomustard"
  },
  "rect": {
    "x": 0,
    "y": 0,
    "width": 1920,
    "height": 1080
  },
  "layer": 0,
  "content_fit": "fill",
  "data": "example-key"
}
```

## Write live data

The canvas example binds its `data` field to `example-key`. That value is a data key: a name this canvas item chooses, not the name of the card. Give each canvas item its own key when items should show different data, or share one key when they should show the same data. Keys are scoped to the project, follow the K/V key grammar, and cannot start with `feed:`.

Create this document before showing the card, then replace it to update the screen without republishing. Writes to a key that live canvas items bind are checked against each bound card’s dynamic properties. Use the same project as the playlist.

Save the document as `card-data.json`. The CLI reads the document itself, with no wrapper:

```json
{
  "footnote": "",
  "updatedAt": "",
  "specials": [],
  "exceptions": []
}
```

```console
screenrig card-data put example-key --file card-data.json
```

Or call the API directly. The API wraps the same document in a `document` field. An agent token already names its project, so no project header is sent; if you send `ScreenRig-Project`, it must match the token’s project. Supply your API authorization through the environment; see [API authentication](/docs/authentication/).

```console
curl --request PUT "https://api.screenrig.ai/api/card-data/example-key" \
  --header "Authorization: Bearer $SCREENRIG_TOKEN" \
  --header "Content-Type: application/json" \
  --data '{"document":{"footnote":"","updatedAt":"","specials":[],"exceptions":[]}}'
```