API changelog
Additions and changes to the public API at /v1. Most changes are additive. Changes that can affect a working integration are called out.
November 12, 2026
Webhook payloads on events. Events from a webhook source can now carry the whole payload Kontakt received, as payload, so journeys read any field as trigger.event_properties.payload.<path>. It is on for new sources and can be ticked on existing ones. Payloads over 64 KB are left off. Failed deliveries can now be retried after you fix a source's mapping. See Webhook sources.
November 11, 2026
Signed webhook sources. A webhook source can now require a signing secret. With one set, each post must carry the hex HMAC-SHA256 of the raw body in the X-Kontakt-Signature header, or it gets 401. Sources can also copy payload fields into event properties, and you can rename, change the address of, switch off, or delete a source in the app. Changing a source's address or deleting it makes the old URL return 404. See Webhook sources.
October 30, 2026
Click and open events. A tap on a tracked link in an email, SMS, or WhatsApp message now records message.clicked on the person, and an email open records email.opened. Both have source system and carry broadcast_id or campaign_id, plus execution_id and step_id for journey messages. Journeys can start on them, wait for them, or count them as goals. See Journeys.
October 29, 2026
Tracked template buttons. When a template's link button has Track clicks turned on, POST /messages/whatsapp fills it with a short link for each person, so you don't send a value for it. The text you send in variables is not changed. See Tracked links.
October 26, 2026
Live chats expire after 24 hours. POST /messages/whatsapp now skips with reason: human_live only when the conversation is open and a teammate took it over or replied in the last 24 hours. A conversation left open after an older handoff no longer holds messages back, so some sends that were skipped before now go out.
October 23, 2026
Send a WhatsApp template. New POST /messages/whatsapp sends one approved template to one person, found or created like POST /events. It follows opt-outs, the contact policy, and live chats, and answers 201 when sent or 202 with a reason when held back. Retries with the same Idempotency-Key or X-CIO-Idempotency-Key don't send twice. See Send WhatsApp from your systems.
Tags from the API. POST /events and POST /customers accept tags (or add_tags) and remove_tags, as an array or a comma-separated string. Missing tags are created. When you send either, the response includes tags with the person's full list. See Ingestion.
Local phone numbers. POST /events, POST /customers, POST /leads, and POST /identify now save phones in E.164. A number without a country code, such as 08030000000, gets the workspace's country code, or the code for its timezone if no country is set. This can affect a working integration: a person you created earlier with a local number is moved to the E.164 form the next time that number arrives, and phone in responses is returned in E.164.
Idempotency header. POST /events reads the Idempotency-Key header, then X-CIO-Idempotency-Key, when the body has no idempotency_key. Two retries that arrive at the same moment now both return the first event instead of one failing with 500.
User ID in journeys. The user_id you send is available in journey messages and steps as {{customer.user_id}}.
Events Kontakt records. A WhatsApp reply to a template now records whatsapp.replied, and a WhatsApp opt-out or opt-in records opted_out or opted_in. They show on the person's timeline with source system, and journeys can start on them, wait for them, or exit on them. A wait step that ends on an event exposes it as {{ nodes.<step>.event_name }} and {{ nodes.<step>.event_properties }}. See Journeys.
October 22, 2026
Rate limits. Each API key can now make 1,000 requests per minute across all /v1 endpoints. Every response carries RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and RateLimit-Policy headers. Over the limit, the API answers 429 with the code RATE_LIMIT_EXCEEDED and a Retry-After header in seconds. This can affect clients that send large bursts: pace backfills from a queue and retry after Retry-After. See Rate limits.
Wallet switched off. When a workspace turns its loyalty wallet off, the wallet credit and debit endpoints answer 409 with the code wallet_disabled and change no balance. See Loyalty wallet.
API reference fix. The OpenAPI spec now shows that GET /ping needs an API key, which it always has, and lists the 429 response on every endpoint.
October 18, 2026
Switch off event sources. Every event now records the API key, store, or webhook source that sent it. Workspace admins can switch off a whole API key, or a single event from it, under Events / Sources.
When a call is switched off, POST /events, POST /leads, and POST /orders answer 202 instead of 201 and store nothing:
{ "data": { "event_name": "commerce.order_placed", "ignored": true, "reason": "event_off" } }
reason is source_off when the whole key is off and event_off when only that event is. POST /orders returns order_id instead of event_name. Use this when the same activity arrives twice, for example orders from a connected Shopify store and again from your backend.
October 4, 2026
Referrals.
GET /customers/{id}/referralreturns the person's referral membership, including their code, for the newest active programme. Passprogram_idto choose another programme.POST /referrals/attributelinks a referee to a referrer by Kontakt customer ID.POST /identifyacceptsreferred_by_codeto credit a referrer when an anonymous visitor signs up.
Push devices. POST /customers/{id}/devices registers a Firebase Cloud Messaging token for the Send Push journey step. Send "unregistered": true to remove it.
Webhook sources. A no-code way to receive JSON from other systems as customer events, outside /v1. See Webhooks.
October 2, 2026
Orders. POST /orders records an order from any store and feeds the same purchase history, journeys, and attribution as a connected Shopify store. Orders are matched on store_id and order_id, so sending one again updates it. New orders record commerce.order_placed, and status changes record commerce.order_paid and commerce.order_fulfilled.
Consent. POST /consent sets a person's consent for whatsapp, sms, email, or rcs. POST /customers also accepts a consent array.
SMS senders. GET /sms/senders lists your SMS sender IDs and their registration status on each network.
September 23, 2026
Events create and update people. POST /events now creates the person when no one matches the user_id, email, or phone you send, and applies a new traits object to their profile. Set upsert_customer: false to keep the old lookup-only behaviour. Empty-string traits are ignored, and traits.whatsapp_opt_in sets WhatsApp opt-in. The response adds customer_created and warnings.
August 12, 2026
Kontakt customer ID as identity. POST /customers and POST /leads accept customer_id, such as an ID carried by a tracked link. It takes priority over other identity fields, and a conflicting email, phone, or user ID returns 422.
August 6, 2026
Leads. POST /leads captures form submissions and records a lead_captured event without opening a conversation. It accepts a plain body or a form tool's webhook payload as is, including nested data wrappers, field arrays with labels, and hidden UTM fields.
March 4, 2026
First release of the public API. POST /customers, POST /events, and POST /identify for people, events, and anonymous visitors. Wallet endpoints for balances, credits, debits, and transactions. POST /codes/validate and code batch stats. GET /ping to check your key.
Not yet available
Outbound webhook subscriptions are not self-serve yet. See Webhooks for alternatives.