Site · Data
Site database items introduction
Last updated 18 November 2026
One row in a database: what items are, where to manage them, and how code reads them.
A database item is one row in a database. If a database of cars has the fields Make, Model and Series, each car you add is one item. You add, edit, import and export items in the admin, and your pages read them to show content.
| Make | Model | Series |
|---|---|---|
| Mazda | RX7 | FD3S |
| Porsche | 911 | 993 |
Each row in this table is one item in a database called Cars.
Where to find items
In the admin, open Data, choose Databases, then open a database's items. From there you can add an item, edit one, import items from a file, export them, view recently deleted items, or empty the database.
Items from code
The Data API gives full create, read, update and delete on items at /databases/api/v2/. Each item comes back as an id, its properties, and its created and updated times. Defining the database and its fields is done in the admin only; the API cannot change a database's fields.
Example: count items with GraphQL
Query
{
admin_tables(per_page: 3) {
total_entries
results { name }
}
}Response on the docs site
{
"data": {
"admin_tables": {
"total_entries": 28,
"results": [
{ "name": "ds_page_feedback" },
{ "name": "ds_promo" },
{ "name": "ds_search_event" }
]
}
}
}This ran read-only on the docs.insites.io site on 1 November 2026, which has 28 tables.
Common mistakes
- Expecting a deleted item to vanish at once. Deleted items are kept for 30 days under recently deleted items.
- Searching the items list in the API by a field value. The list only honors a keyword search, and a search with no match answers 404.
- Expecting a webhook when an item changes. The Data module sends none.