Overview
Inklura's marketing and support features are delivered by tool apps (SMS Designer, Mail Designer, SEO, the console). Depending on the feature, you drive them in one of two ways:
| Surface | Address | Typical use |
|---|---|---|
| Platform API (tRPC) | https://manage.inklura.fr/api/trpc/* |
Email campaigns, campaign analytics, journeys, knowledge base. |
| A tool app's routes | e.g. https://smsdesigner.inklura.fr/api/* |
A tool's own actions: SMS campaigns, SEO reports. |
The Platform API is documented under Platform API; its calling
conventions (superjson envelopes, result.data.json, Bearer auth) apply to every tRPC
procedure named in this section. The tool app routes named in this section are protected by
the signed-in user's session (a cookie set when signing in to the tool, not a Bearer token):
without that session, they reject the request.
If you build your own app on the framework, storage and background work go through the SDK: see the SDK Overview, KV, Queue, and Tasks.
The integration surfaces
| Surface | Primary entry point |
|---|---|
| SMS campaigns | POST /api/campaigns (SMS Designer) |
| Email and MJML | campaigns and emailAnalytics routers, Mail Designer |
| Marketing journeys | journeys router |
| SEO reports | POST /api/seo/reports (SEO app) |
| Helpdesk and knowledge base | helpdeskKb router, console /manage/helpdesk |
What is automatic and what is not
Some features are partial. Keep this in mind before you build on them.
The SMS delivery rate is entered by hand. The SMS carrier does not send delivery receipts. On reports, "Delivered" shows a benchmark estimate (95%) until someone enters the real figure, and "Read" is always an estimate. Clicks are measured. See SMS Campaigns.
In a journey, only the EMAIL step acts. The SMS step is skipped, and the WEBHOOK,
UPDATE_FIELD, ADD_TO_SEGMENT, REMOVE_FROM_SEGMENT, CREATE_TASK, and
SEND_NOTIFICATION steps only move the contact forward. A WEBHOOK step does not emit an
outbound request. WAIT, CONDITION, and GOAL do nothing when they run (the wait comes from
each step's delayMinutes), and CONDITION does not evaluate any branch. See Marketing Journeys.
SMS scheduling is handled by the carrier. A scheduled SMS campaign is handed to the carrier with its send time, and the carrier fires it.
Where to next
| Page | What it covers |
|---|---|
| SMS Campaigns | The /api/campaigns action API, scheduling, delivery rate, public reports |
| Email and MJML | Mail Designer, the campaigns and emailAnalytics routers, open and click tracking |
| Marketing Journeys | The journeys router, triggers, step types, templates, and enrollment |
| SEO Reports | Data sources and report generation (POST /api/seo/reports + SSE) |
| Helpdesk and Knowledge Base | The helpdeskKb router and tickets |
Connect Mahalo
Opper / Mahalo connector — Opper-compatible transactional API, Mahalo setup and delivery events.