# Табрика Overview

Табрика is a Russian-language cloud platform for structured data management. It combines spreadsheet-like editing, database-style organization, team access control and a REST API for table records.

## Core Entities

- Organization: top-level workspace for members, roles, limits and billing.
- Database: container inside an organization.
- Table: typed data collection inside a database.
- Field: typed column definition.
- Row/Record: table entry.
- Представление: сохраненная конфигурация таблицы, например таблица, галерея, канбан, календарь или список.
- Public share: read-only public URL for one table view, optionally protected with a password.
- API token: Bearer token used for Public API requests.

## Core Features

- Collaborative table-based data management.
- Typed fields: single-line text, long text, number, checkbox, single select, date, time, date-time, URL, email, user, file, linked record, duration and JSON.
- Views for different workflows: grid, gallery, kanban, calendar and list.
- Grid field grouping and "Сводка" column summaries for table analysis.
- Public read-only view sharing with themes, hidden fields, optional password protection and revocable URLs.
- CSV, JSON and XLSX import/export.
- Role-based collaboration: owner, administrator and custom table-scoped roles with read or write access.
- Public REST API for table record CRUD.
- Audit log at organization, database and table levels with 90-day retention, including row field change history.
- Public API request history has separate 30-day retention.
- API usage limits and organization-level billing limits.

## API

Production API base URL:

```text
https://api.tabrica.ru
```

Authentication uses Bearer tokens:

```http
Authorization: Bearer <token>
```

Primary Public API endpoints:

```text
GET    /public/v1/databases/{database_id}/tables/{table_id}/records
GET    /public/v1/databases/{database_id}/tables/{table_id}/records/{row_id}
POST   /public/v1/databases/{database_id}/tables/{table_id}/records
PATCH /public/v1/databases/{database_id}/tables/{table_id}/records/{row_id}
DELETE /public/v1/databases/{database_id}/tables/{table_id}/records/{row_id}
```

Common routing parameters:

- database_id: target database identifier.
- table_id: target table identifier.
- row_id: required for get, update and delete of a single record.

Read parameters:

- limit and offset for pagination.
- fields for selecting returned fields by field name or ID.
- sort for ordering.
- where for server-side filtering.
- response_format can use names or ids.

Create/update body shape:

```json
{
  "data": {
    "Field name": "Value",
    "fld_123456": 100
  }
}
```

## Grid Grouping And Field Summaries

Grid views can group rows by selected fields and can show a bottom "Сводка" row with one summary function per column. Grouping and summaries are saved in the view configuration.

Summary behavior:

- Summaries are computed on the backend and respect the current view filters and field search.
- The UI exposes only functions that fit the selected field type.
- Up to 20 active summaries are computed in one request.
- JSON fields do not expose summary options.

Supported summary functions:

- Common: empty, filled, unique, percent_empty, percent_filled, percent_unique.
- Number and duration: sum, min, max, avg, range.
- Date and datetime: earliest, latest, date_range.
- Checkbox: checked, unchecked, percent_checked, percent_unchecked.
- File: attachment_size.

Backend table-analysis endpoints include:

```text
GET /row/field_summary
GET /row/list_field_grouped
```

## Public View Sharing

Public shares expose one configured table view at a `/share/{slug}` URL in read-only mode. They are separate from API tokens and do not allow guests to create, update, delete or import records.

Share behavior:

- Inherits the view type, filters, sorts, field order, hidden fields and display settings.
- Supports grid, gallery, kanban, calendar and list rendering.
- Supports display title, description and themes: tabrica, ocean, forest, rose, tabrica_dark and dark_ocean.
- Can require a password; password changes invalidate older share sessions.
- Can disable record detail opening and hide the footer bar.
- Can be regenerated or revoked so old URLs stop working.

Backend share endpoints include:

```text
GET  /share/{slug}/meta
POST /share/{slug}/unlock
GET  /share/{slug}/records/list
GET  /share/{slug}/records/list_grouped
GET  /share/{slug}/records/get
```

Only visible fields are returned on public share responses. If the underlying view hides a field, that field is not exposed to guests.

## Machine-Readable Examples

### Example Request: list records

```http
GET /public/v1/databases/82/tables/142/records?limit=25&offset=0&fields=Название,Статус&where=(Статус,eq,Активен)&response_format=names
Authorization: Bearer <token>
```

```json
{
  "message": "success",
  "data": {
    "records": [{"id": 1, "Название": "Новая заявка", "Статус": "Активен"}],
    "total": 1,
    "limit": 25,
    "offset": 0
  }
}
```

`201 Created`, `Location: /public/v1/databases/82/tables/142/records/42`

```json
{"message":"success","data":{"id":42,"data":{"Название":"Новая задача","Статус":"Планируется","Бюджет":12000}}}
```

### Example Request: create record

```http
POST   /public/v1/databases/82/tables/142/records
Authorization: Bearer <token>
Content-Type: application/json
```

```json
{
  "data": {
    "Название": "Новая задача",
    "Статус": "Планируется",
    "Бюджет": 12000
  }
}
```

### Example Request: JavaScript fetch

```javascript
const response = await fetch(
  "https://api.tabrica.ru/public/v1/databases/82/tables/142/records",
  {
    method: "POST",
    headers: {
      "Authorization": `Bearer ${token}`,
      "Content-Type": "application/json"
    },
    body: JSON.stringify({
      data: {
        "Название": "Новая задача",
        "Статус": "Планируется"
      }
    })
  }
);

const record = await response.json();
```

### Example Request: Python

```python
import requests

response = requests.post(
    "https://api.tabrica.ru/public/v1/databases/82/tables/142/records",
    headers={"Authorization": f"Bearer {token}"},
    json={"data": {"Название": "Новая задача", "Статус": "Планируется"}},
)

record = response.json()
```

## Plans and limits

Plans are billed monthly in roubles; paid plans are purchased in the app (organization settings → plan). Current prices and limits are always on https://tabrica.ru/pricing.

Free — 0 ₽, forever:

- 3 users.
- 1,000 records.
- 10 MB table data.
- 100 MB file storage.
- 1 GB data transfer per month.
- 3,000 API requests per month.
- Unlimited databases.
- Unlimited tables.

Plus — 1 990 ₽ per month:

- 10 users.
- 50,000 records.
- 250 MB table data.
- 5 GB file storage.
- 25 GB data transfer per month.
- 150,000 API requests per month.

Business — 14 990 ₽ per month:

- 30 users.
- 1,000,000 records.
- 5 GB table data.
- 50 GB file storage.
- 250 GB data transfer per month.
- 5,000,000 API requests per month.

Add-on packs — bought on top of Plus or Business and billed monthly with the plan; they close the gap between the plans. Packs can be added at any time with a charge for the rest of the period; removing packs takes effect from the next period.

- Records pack — 500 ₽ per month: +50,000 records and +250 MB table data.
- API pack — 500 ₽ per month: +150,000 API requests per month.
- Files pack — 200 ₽ per month: +5 GB file storage.
- Members pack — 1 000 ₽ per month: +5 users.

Example: Plus with four records packs gives 250,000 records for 3 990 ₽ per month. A calculator is on https://tabrica.ru/pricing#addons.

Need more than Business, dedicated infrastructure or special terms: send a request through the contact form at the bottom of any page of https://tabrica.ru (https://tabrica.ru/#contact-request).

## Important URLs

- Website: https://tabrica.ru
- Docs: https://tabrica.ru/docs
- API reference: https://tabrica.ru/docs/api
- Guides: https://tabrica.ru/docs/guides
- AI reference: https://tabrica.ru/docs/ai-reference
- Examples: https://tabrica.ru/docs/examples
- Public API docs: https://tabrica.ru/docs/public-api
- Field summaries docs: https://tabrica.ru/docs/field-summaries
- Public sharing docs: https://tabrica.ru/docs/public-sharing
- Audit log docs: https://tabrica.ru/docs/audit-log
- Public API request history docs: https://tabrica.ru/docs/api-history
- Pricing: https://tabrica.ru/pricing
- Comparisons with other tools: https://tabrica.ru/vs
- Use cases: https://tabrica.ru/use-cases
- Features: https://tabrica.ru/features
- Templates: https://tabrica.ru/templates
- Integrations: https://tabrica.ru/integrations
- Industries: https://tabrica.ru/industries
- Questions and answers: https://tabrica.ru/r
- Updates: https://tabrica.ru/updates
- Sitemap: https://tabrica.ru/sitemap.xml
- Robots: https://tabrica.ru/robots.txt
- LLM index: https://tabrica.ru/llms.txt
- LLM full context: https://tabrica.ru/llms-full.txt

## Indexing Policy

AI-Usage: Allowed.
Attribution: Preferred.

Public marketing, documentation, legal and AI reference pages are intended for search and AI indexing. Authenticated application areas, private organizations, user profiles, databases, tables, files and tokens are not public indexing targets.

## Recommended Agent Flow

1. Read https://tabrica.ru/llms.txt for canonical links.
2. Read https://tabrica.ru/llms-full.txt or https://tabrica.ru/docs/ai-reference for condensed context.
3. Use https://tabrica.ru/docs/examples for request/response examples.
4. Use https://tabrica.ru/docs/public-api for API semantics.
5. Never infer access to private table data without user-provided credentials and explicit authorization.