Cards
The cards of one area, in their order.
GET /api/data/cards
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
areaId | integer | yes | The area whose cards you want. |
curl -X GET "https://boards.example.com/api/data/cards?areaId=10" \
-H "X-API-Key: $LOKALBOARDS_KEY"
Response
{
"cards": [
{
"id": 501,
"area": 10,
"name": "Redesign the logo",
"content": "Refresh the brand mark for the 2.0 launch.",
"status": 0,
"sort": 0,
"dueDate": "2026-08-21T19:31:00.000Z",
"repeatEvery": null,
"assignees": [
{
"id": "8f3c1e2a-5b7d-4a91-9c8e-2d6f0b4a7e13",
"name": "Anna",
"image": null,
"type": "human"
}
],
"assignee": "8f3c1e2a-5b7d-4a91-9c8e-2d6f0b4a7e13",
"assigneeName": "Anna"
}
]
}
assignees is everyone on the card, in the order they were put on it — a card
can be on several people. assignee, assigneeName, assigneeImage and
assigneeType describe the first of them, as they did before, so an
integration that only knows one person per card keeps reading a sensible
answer. ?assignee=<id> finds a card by any one of its people, and
?unassigned=true finds cards nobody is on.
status is 0 for open and 1 for done. content is Markdown — a - [ ]
line in it is a checklist item, and the counts on the card's tile come from
those. See Cards.