Skip to content

Mobile apps

Kontakt doesn't have a mobile SDK. Your app, or better your backend, talks to Kontakt through the same API your other systems use.

If you run your own mobile app, you can send Kontakt who your users are, what they do in the app, and which devices should get push notifications. There is no library to install. Your app or server calls a few API endpoints, and journeys react to what it sends.

Looking for the Kontakt app for your team?

This page is about connecting your own customer-facing app. The Kontakt mobile app is for your team: it shows Conversations and takes WhatsApp calls. See WhatsApp calling.

Before you start

  • A workspace API key from Settings / API Keys. Keys start with pk_live_ or pk_test_ and go in the Authorization: Bearer header.
  • A developer who can add API calls to your app or its backend.
  • For push, a Firebase project. See Push notifications.

Keep the API key on your server

An API key gives access to your workspace data. Make these calls from your backend, not from code shipped inside the app, where anyone could extract the key.

Connect your app

Create or update the person

When a user signs up or logs in, call POST /v1/customers with their user_id (your own ID for them), email, or phone, plus any properties. Kontakt finds the existing person or creates one, and returns the Kontakt customer ID. Store it with your user.

Track what they do

Send in-app actions with POST /v1/events, for example purchase_completed with its properties. Events can start journeys with the Event Occurs trigger. Add an idempotency_key so a retried call doesn't record the event twice. See Events.

Link anonymous users when they log in

If you created a person before you knew who they were, call POST /v1/identify with their anonymous_id and the known user_id, email, or phone. Kontakt merges the anonymous profile into the known one.

Record consent

When a user opts in or out of marketing on a channel, record it with POST /v1/consent. Marketing SMS and email only go to people with consent on that channel.

Register push devices

Send each device's Firebase registration token with POST /v1/customers/{id}/devices, and unregister it when the user signs out. See Push notifications.

How it behaves

  • Identity. A person is matched by Kontakt customer ID first, then by your user_id, email, or phone. Sending the same identity again updates the person instead of creating a duplicate.
  • Properties. Standard keys such as first_name and last_name update the profile. Other keys become custom fields. See Fields and tags.
  • Events switched off. If an event or API key is turned off under Events, the API answers that it was received but stores nothing and starts no journey.
  • No in-app chat. There is no chat component for your app. To offer chat, link to your WhatsApp number, or show your website with the web widget in a web view.

FAQ

Is there an SDK for iOS, Android, React Native, or Flutter?

No. Use the REST API from your backend.

Can Kontakt send in-app messages or banners?

No. Kontakt can send push notifications to your app through your Firebase project.

Where is the full list of endpoints?

See the API reference and Ingestion.