#Glossary

Status: Available.

Sapport platform terms in alphabetical order. Pages that cover a term in more detail are shown in parentheses.

Agent (CRM agent). An automated executor of the AI seller and the CRM: creates a lead, changes a status, scores a lead, sets tasks, hands a conversation over to an operator. In an external CRM, the agent does not change a status itself but sends an "action request" (Action requests).

api_access. A license flag that permits programmatic access.

API key. A secret string sap_<cell>_<mode>_<identifier>_<secret>. Shown once. Stored only on the client side (see Authentication).

Attribution. Determining where an inquiry came from: UTM tags, a visit from search or from an AI answer, an ad click, the first touch. Stored in the conversation, the contact, and the lead.

Beacon. A short request that records a page visit. There are two kinds: the JS beacon from the browser and the signed server beacon from the CMS (which sees bots and AI crawlers) (analytics/04-js-tracker.md).

Cell. An independent production copy of the platform with its own database, secrets, and legal entity: RU, EN, ID (see Cells and data).

Channel. A source and destination of conversations: a web chat on a site, a messenger, the tenant's own channel (the api channel). The web chat channel identifier (channel_id) is public and is embedded in the site code.

Connector. The protocol and modules that link the platform to a tenant's CMS: the signed server beacon, the loader, article publishing. Modules exist for Bitrix and WordPress; FastAPI and Nuxt are not published (analytics/03-cms-modules.md, articles/03-publishing-modules.md).

Contact. A person the platform communicates with: full name, email, phone, tags, history. Contains personal data.

CRM mode. A tenant setting: internal (our CRM), external (the source of truth is the external CRM after a lead is accepted), both (field by field) (crm/01-modes.md).

Cursor. A signed marker of a position in a list (next_cursor). Opaque to the client (see Conventions).

Data controller. The party that determines the purposes and means of processing personal data. For a tenant's customer data, this is the tenant; the platform acts as the data processor on the tenant's instructions (see Cells and data).

Dead letter. A webhook delivery that was not accepted even after the eighth retry. It stays in the delivery log and can be resent (Webhooks).

Disclosure log (personal data). A record of every disclosure of personal data through the API: who, what, how many records; without the values. Visible to the tenant in the dashboard and through GET /disclosures, retained for 3 years (Cells and data).

Editorial profile. Tenant settings for article generation. Without it, generation is unavailable (editorial_profile_required).

First touch. The source from which a visitor first came to the site: UTM, click identifiers, landing page, referrer.

Idempotency. A property of an operation: repeating it with the same Idempotency-Key does not create a duplicate (see Conventions).

include_pii. A webhook subscription flag: includes personal data in lead.*, contact.*, and conversation.* events. false by default (Webhooks).

Integration. A tenant service account for programmatic access. No dashboard login, its own role; owns the API keys (see Authentication).

Lead. A potential deal tied to a conversation and a contact: status, score, source, value, owner. A lead always exists on the platform; only the party that owns its fields changes (crm/01-modes.md).

livemode. An event envelope field: true for production data, false for test events (webhook.test) and the sandbox.

Loader. The script loader.js?k=<public key>: in one line it connects the JS tracker, behavior collection, the chat, and consent management (analytics/02-loader.md).

Operation (operation). The single envelope for asynchronous work: 202 {operation: {id, type, status, …}}. Statuses: queued, running, succeeded, failed, canceled. The result is available through GET /operations/{id}, the ?wait parameter (up to 20 s), or the operation.completed event (Conventions).

Paid operation. A call that charges money to the wallet (see Conventions).

Personal data (PII). Name, email, phone, and the like. Scopes that involve personal data are marked in the table in Authentication.

problem+json. The application/problem+json error format per RFC 9457 (see Conventions).

Publisher. The module for generating, approving, and publishing articles to a tenant's site (articles/).

request_id. The request identifier from the X-Request-Id header and the error body; support needs it.

Sandbox. A cell test tenant with fictitious data for test keys. Status: Planned.

Scope. A permission granted to a key, for example leads:read. The effective permissions of a request are the intersection of the key's scopes, the integration's role, the owner's current permissions, and the plan.

Session (chat). A signed widget visitor token; lives in the browser for up to 30 days, signed but not encrypted.

Strategist. The AI marketer: regular reports with evidence and expected impact, a topic queue, chat actions, conversation (Strategist).

Strategist action. A pending action that the strategist proposed in the chat: proposed → confirmed → executed or failed; it can be canceled (cancelled) or expire after 7 days (expired). It is confirmed and canceled through /strategist/actions (Topics and actions).

Strategist topic. An item in the article topic queue that the strategist proposes: it is approved or rejected (/strategist/topics). Approval does not start article generation (Topics and actions).

Tenant. A customer organization of the platform: its data, keys, wallet, staff, and sites. It is determined only by the API key and never by request parameters (see Authentication).

Thin payload. A webhook event that contains only identifiers and a type, with no personal data (see Webhooks).

Tombstone. A record {id, deleted_at} about a deleted resource that a list returns when include_deleted=true; retained for 30 days (Conventions).

usage. The block {cost: {amount, currency}, model} in responses of paid operations and in operation: how much was charged and which model performed the work (Conventions).

Wallet. The tenant's balance in the currency of its cell. Charges for paid operations are deducted from it: AI replies, lead scoring, article generation, strategist turns.

Webhook. An outgoing platform event delivered to your HTTPS address with a Sapport-Signature signature (see Webhooks).