Send any text, get a 1–10 sentiment score back
Built for developers integrating their own helpdesk, CRM or product: POST one event to SentiTrack's /ingest API and it flows into the same Net Graph, Time Graph, Reports and Alerts as every other channel. If it's text, SentiTrack can score it.
The SentiTrack ingest API is a per-org, API-key-authenticated REST endpoint (POST /api/v1/ingest/sentiments) that accepts any text message from your own helpdesk, CRM or product and turns it into a 1–10 sentiment event. One call becomes one record that flows into your Net Graph, Time Graph, Reports and Alerts.
Your most honest signal is trapped in custom systems
Email, calls and chat are covered out of the box — but the tone inside your own helpdesk tickets, CRM notes and in-product messages never reaches your dashboards. Without a way to push those messages in, every custom channel stays a blind spot, and the friction building there shows up only after it costs you a customer or a teammate.
A single endpoint for anything that is text
The /ingest API gives developers a tenant-scoped way to feed any message into SentiTrack. Authenticate with a per-org API key, POST an event with a source channel, from, to and the text, and SentiTrack scores it 1–10 and routes it into the same analytics pipeline as email, voice and chat. Bodies are scored, then discarded — only the score, participants, timestamp, direction and a subject hash are kept.
- Per-org API key auth — every event is scoped to your tenant, never to a client-supplied org_id
- Pick any source channel: email, phone, slack or a custom key your org defines
- Send an external_id for safe idempotent retries — duplicates are deduplicated, not double-counted
- Single events or bulk batches of up to 500, so a backfill is one job, not thousands of calls
From your system to your graph in three steps
In Settings, generate a per-org ingest key. The plaintext is shown once; SentiTrack stores only a prefix and a hash. Call GET /api/v1/ingest/whoami to confirm the key resolves to your organization before you wire it in.
Send one event to /api/v1/ingest/sentiments with a source channel, from, to (and optional cc), the message text and an optional external_id. SentiTrack scores the text 1–10 with the bundled SentiAI engine, or you can pass a score you already computed.
The event becomes one record with a topic, direction and participants — instantly visible in the Net Graph, Time Graph, Topic clusters, scheduled PDF Reports and Alerts, alongside email, voice and chat. No separate dashboard, no extra setup.
Helpdesk tickets, CRM notes, in-product messages, reviews, support transcripts — anything textual becomes a 1–10 sentiment event. One contract covers every custom source you can think of.
Ingested events flow through the identical pipeline as email, voice and chat, so they appear in your Net Graph, Time Graph, Topic clusters, Reports and Alerts with zero additional configuration.
Authentication is a per-org API key, and every event is scoped server-side to that organization. Client-supplied org identifiers are never trusted, so cross-tenant leakage is structurally impossible.
Pass an external_id and retries are safe — a repeat call returns the existing record instead of duplicating it. Backfill history with bulk batches of up to 500 events per request.
The same 7-language native scoring applies — English, German, French, Italian, Spanish, Russian and Turkish, plus Arabic — with no per-language setup or routing on your side.
Bodies are scored then discarded. SentiTrack keeps only the score, participants, timestamp, direction and a subject hash — never the message text, subject or attachments you sent.
We score the text, then throw it away
The ingest API inherits SentiTrack's whole-platform privacy posture. Whatever message you POST is scored and then discarded — it is never persisted. We retain only the 1–10 score, the participants, the timestamp, the direction, the topic and a subject hash, so your custom-channel data carries no more risk than email.
- Zero message bodies, subject text or attachments stored — only score plus metadata
- Per-org API keys are Fernet-encrypted at rest; only a prefix and hash are kept after creation
- Configurable retention (default 365 days) and a hard-delete endpoint apply to ingested events too
- Storing sentiment with demographic attributes can be GDPR Article 9 data — DPIA, lawful basis and consent remain the customer's responsibility under the ToS
Developer ingest API — FAQ
How do I send sentiment data to SentiTrack programmatically?
POST a JSON event to /api/v1/ingest/sentiments authenticated with a per-org API key. Include a source channel, from, to and the message text, and SentiTrack scores it 1–10 and routes it into your dashboards. For history, /ingest/sentiments/bulk accepts up to 500 events in a single best-effort batch.
Does the ingest API store the message body?
No. The ingest API follows the same privacy posture as every SentiTrack channel: the text is scored, then discarded. Only the 1–10 score, participants, timestamp, direction, topic and a subject hash are stored — never the message body, subject text or attachments you send.
How is the ingest API authenticated?
With a per-org API key you generate in Settings. The plaintext key is shown once at creation; SentiTrack stores only a prefix plus a hash. Every event is scoped server-side to the organization that owns the key, so a client-supplied org_id is never trusted and tenants cannot leak into each other.
Can I retry a request safely without creating duplicates?
Yes. Pass an external_id with each event and ingestion becomes idempotent: a repeat call with the same {org, external_id} is deduplicated and returns the existing record rather than creating a second one. This makes retries, replays and at-least-once delivery from your queue safe to wire up.
What kinds of messages can I push to the ingest API?
Anything textual. Helpdesk tickets, CRM notes, in-product chat, support transcripts, reviews and custom channels all work — if it's text, SentiTrack can score it. Tag each event with a source channel (email, phone, slack or a custom key) so it groups correctly in your Net Graph and Time Graph.
Do ingested events show up in the same graphs as email?
Yes. Each ingested event becomes one record that flows through the identical pipeline as IMAP email, voice and chat. It appears in the Net Graph, Time Graph, Topic clusters, saved views, scheduled PDF Reports and Alerts with no separate dashboard and no extra configuration on your side.
Wire your first message in today
Generate a per-org API key, POST one event, and watch it land in your Net Graph and Time Graph. Or open the live demo with sample data — no signup required — to see exactly where your ingested messages appear.