Data Stores

Returns a list of all data stores (tables) available for a specific application. This includes built-in stores (customers, services, etc.) and any custom-defined schema tables.

Each entry in the returned array contains at minimum key (string store identifier), label (human-readable name), and fields (list of field definitions). Built-in store keys: customers, appointments, services, feedback, personnel, promotions, campaigns, time-slots.

Retrieves all records from a specific storage table (built-in or custom). The result structure depends on the schema of the requested store.

By default this endpoint keeps the legacy response shape and returns a plain JSON array. When page, size, q, field, or field.<key> is provided, it returns a paginated object: {content, currentPage, pageSize, totalItems, totalPages}.

Search/filter examples:

• ?q=acme&page=0&size=25 searches across returned fields.
• ?field=phoneNumber:+15551234567&page=0&size=1 filters by one exact field.
• ?field.phoneNumber=+15551234567&page=0&size=1 is equivalent and easier for URL builders.
• For massive custom stores, prefer size=500 and pass the returned nextCursor as cursor on the next request instead of incrementing page.

Built-in store keys and their record shapes:

• customers — {id, name, email, phone, notes, createdAt, updatedAt, ...}
• appointments — {id, customerId, serviceId, personnelId, startTime, endTime, status, notes, createdAt, ...}
• services — {id, name, description, duration, price, createdAt, ...}
• feedback — {id, customerId, rating, comment, callId, createdAt, ...}
• personnel — {id, name, role, email, phone, createdAt, ...}
• promotions — {id, name, description, discount, validFrom, validTo, createdAt, ...}
• campaigns — {id, name, description, startDate, endDate, status, createdAt, ...}
• time-slots — {id, dayOfWeek, startTime, endTime, maxCapacity, createdAt, ...}
• custom keys — {id, createdAt, updatedAt, ...plus all custom fields defined in the store schema}

Inserts one record into a custom application data store. Built-in stores are read-only through this external endpoint; use a custom store for integrator-managed customer datasets.

Send custom fields at the top level. Reserved fields are handled specially:

• customerId / customer_id links the record to an existing customer in the application.
• metadata / metaData / meta_data stores machine-readable metadata beside the record.
• id, createdAt, and updatedAt are ignored on write.

Replaces the custom-field payload for one record in a custom application data store. Built-in stores are read-only through this external endpoint.

Send the full desired custom-field object. If metadata is present it replaces the record metadata; if customerId is present it relinks the record to that application customer.

Deletes one record from a custom application data store. Built-in stores are read-only through this external endpoint.

Returns the configured custom fields for a custom data store and whether the backing Postgres expression index exists for fields marked indexed.

Returns ingestion counters and recent ingestion events for a custom data store. Use this to monitor enterprise sync jobs and verify whether incoming customer-data feeds are creating, updating, failing, or slowing down.

Upserts many records into a custom data store. Use this for CRM/customer sync jobs instead of sending one HTTP request per row. Each row uses the same where/data/metadata shape as the single-record upsert endpoint.

Maximum batch size is 1000 records. The response includes created, updated, unchanged, and error counts plus per-row errors.

Updates matching custom-store records without first retrieving their ids. Use this for operations such as: update rows where phoneNumber = +15551234567.

where fields must be configured as indexed fields. set is merged into each matched record. Use limit to bound blast radius. Maximum limit is 1000. Set dryRun: true to count and sample matches without writing.

Creates or updates one custom-store record by matching indexed custom fields in where. This is the preferred enterprise ingestion endpoint for customer data keyed by phone number, external CRM id, membership id, or similar identifiers.

where fields must be configured as indexed fields in the data-store settings. By default the endpoint creates a record if no match exists and merges data into an existing record if one match exists. Multiple matches return 409 to protect data quality.

Returns the detailed schema metadata for a specific store key. Includes field definitions, types, and labels used for rendering data.

Each schema object contains: key (string), label (string), and fields (array of field definitions, each with key, label, type — one of text, number, boolean, date, select, multiselect, textarea).