Developers
Business Messaging
Tell your customers about their order, their delivery or their sign-in, in Sika, when they agreed to hear from you. Not open yet: we are building and testing it, and this page says what it will do so you can plan.
What it is, and what it is not
A business notice is not a private chat. Private chats, files and calls stay end to end encrypted and are never touched by this. A notice passes through a Sika service so it can be checked against wording Sika approved and counted, so Sika can read it. In the app it is labelled Business notice and kept apart from private chats. The Privacy Policy and Security pages say the same.
Only people who agreed. A person agrees once when they sign in to your app with Sika, choosing which kinds they want: order updates, login codes, offers. They can stop any business, or any kind, at any time and it stops at once. You cannot send a kind they did not agree to.
Kinds of notice
| Kind | For | Needs |
|---|---|---|
utility | Something the person is already doing: an order, a delivery, a booking, a bank notice. | They ticked order updates. |
login_code | A one-time code for signing in to your app. | They ticked login codes. |
marketing | Offers and news. | They ticked offers, which is off unless they turn it on. Never between 21:00 and 07:00, and never in a private chat. |
A reply the person writes to you is their own private message and arrives through your Sika Chat team as usual.
Templates and review
Every notice uses a template you submit first. The wording is fixed; only numbered slots change. A template is checked automatically (no pressure wording, https links only, slots in order) and a person at Sika reads everything except a plain login code. A declined template comes back with the reason. Editing a template makes a new version that is reviewed again.
curl -X POST https://DEV_HOST/v1/templates \
-H "Authorization: Bearer sika_live_YOUR_KEY" \
-d '{"name": "out_for_delivery", "kind": "utility",
"body": "Your parcel {{1}} is out for delivery. Rider {{2}}. Expected before {{3}}."}'
Send a notice
The to value is the identifier Sika gave your app for that person when they signed in. Send an idempotencyKey for each message so a retry never sends twice.
curl -X POST https://DEV_HOST/v1/notices \
-H "Authorization: Bearer sika_live_YOUR_KEY" \
-d '{"to": "PERSON_ID", "template": "out_for_delivery",
"vars": ["KL-4821", "Tunde", "5 pm"],
"idempotencyKey": "order-4821-out"}'
| Answer | Meaning |
|---|---|
| 201 | Accepted. The body has the notice id and its state. |
403 no_consent | The person has not agreed to this kind, or stopped it. |
409 not_approved | The template is still in review or was declined. |
409 quiet_hours | Marketing is not sent between 21:00 and 07:00. |
429 rate, monthly_cap | Too many this minute, or the month's limit including the burst allowance is reached. |
402 plan | Business Messaging needs a paid developer plan. |
Webhooks
Save an https address with PUT /v1/webhook and Sika sends signed events when a notice is delivered, read, answered or stopped, when a person changes what they agreed to, and when a person taps Talk to a person (handover.requested). Events carry ids and states only, never the wording of a notice. The signature header is Sika-Signature: t=SECONDS,v1=HMAC, the same scheme as the other Sika webhooks, and failed deliveries are retried for about a day.
Reports and limits
GET /v1/reports?days=7 shows, for each template, how many were sent, delivered, read and stopped. GET /v1/usage shows the month against your allowance. A business whose notices are reported by many people loses marketing until Sika has looked.
Each notice's wording is kept for 90 days (a login code for one day) and then only the counts remain.
Who sees what
You see the identifier Sika gave your app for the person, never their Sika key, number or contacts. Sika's notice service sees the notice text, the time and whether it was delivered, read, answered or stopped.
Plans and price
Business Messaging will come with a flat monthly allowance on a paid developer plan, a small per-notice charge for large bursts above it, and login codes priced below SMS. Prices are set when it opens and will be published here first.
Questions
Write to support@sikaos.app. The general developer tools are on the Developers page, and plans for companies are on Sika for companies.