telkit

Use case

For platforms and agencies with many clients

A booking system for hairdressers, an agency running websites, a SaaS for housing co-operatives. You send messages on behalf of many clients, and each of them should have its own name, its own limits and its own bill.

Last reviewed 14 October 2026

The problem

One account for every client mixes up senders, statuses and costs. One account per client leaves you with a hundred contracts and a hundred balances to watch.

At telkit your company is the account, and every end customer is a profile in it. The profile has its own senders, keys, webhooks, contacts and templates, and you see usage per profile. Every profile draws from the same balance.

What a platform gets

You create and manage profiles from the API, so new clients are set up without anyone logging in to the dashboard.
  • Profiles over the APICreate, change and archive profiles with a company key that holds profiles:manage. Each profile switches on the services it uses.
  • Keys per profileA key can cover one profile and only some scopes. With keys:manage your system can mint such keys itself.
  • A monthly limit per profileSet a limit in kroner for each profile. When it is reached, sends from that profile stop, and the others carry on.
  • Webhooks per profileAn endpoint can cover the whole company or one profile. Events always say which profile they belong to.
  • Senders per profileEach profile has its own sender names, its own SMS number and its own letterhead. If a name is a client's brand, you say why you may use it.
  • Usage per profileFetch the usage of one profile for one period, split by service, and invoice your clients yourself.

Example flows

From a new client to the final invoice.

A new client

  1. The client signs up with you. Your system creates a profile with the client's name and a short name (slug).
  2. The system creates a live key that covers only that profile, and sets a monthly limit.
  3. The system registers a webhook endpoint for the profile, and the client can send.

Invoicing at month end

  1. The system fetches usage per service for each profile for the previous month.
  2. The amounts are in øre excl. VAT, the same as telkit drew from the balance.
  3. You add your own margin and invoice your clients.

A client leaves

  1. The system archives the profile.
  2. Every key of the profile is revoked at the same time.
  3. The history stays, so you can answer questions about old messages.

What the request looks like

A new profile, a key that covers only it, and a monthly limit. The calls are made with a company key.
POST /v1/profilesbash
curl https://api.telkit.no/v1/profiles \  -H "Authorization: Bearer $TELKIT_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "name": "Frisør Hansen",    "slug": "frisor-hansen",    "description": "Kunde 2291 i bookingsystemet",    "services": {      "sms": true,      "email": true,      "letters": false,      "phone": false    }  }'
The short name (slug) cannot change later, because your systems use it in their calls.
POST /v1/api-keysbash
curl https://api.telkit.no/v1/api-keys \  -H "Authorization: Bearer $TELKIT_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "name": "Frisør Hansen, booking",    "mode": "live",    "profileId": "…",    "scopes": [      "sms:send",      "sms:read",      "email:send"    ]  }'
The answer holds the whole key. It is shown only here, so store it at once.
PUT /v1/profiles/{slug}/limitbash
curl -X PUT https://api.telkit.no/v1/profiles/frisor-hansen/limit \  -H "Authorization: Bearer $TELKIT_API_KEY" \  -H "Content-Type: application/json" \  -d '{    "limitOre": 50000  }'
limitOre is the limit in øre: here NOK 500 a month. null removes the limit.

What to watch out for

You are telkit's customer. Your end customers are yours.
  • Your company is the one that is verified, and your company is telkit's customer. Make sure your agreements with your clients say what they may send.
  • A sender name that does not point to your company needs a note on why you may use it. We approve every name.
  • Give every end customer a key of their own. You can then revoke one without stopping the others.
  • Set a monthly limit on every profile, so one client cannot use up the balance everyone shares.

What it costs

Profiles cost nothing in themselves. You pay for what is sent, from one balance, at the same prices as everyone else.
SMS sent, per unit
NOK 0.75
Email sent
NOK 0.01
Letter delivered to Digipost
NOK 5
Dedicated SMS number, per month
NOK 490
Phone number, per month
NOK 59

Prices exclude VAT.

Questions from platforms and agencies

Does every profile have its own balance?

No. Every profile draws from the company's balance. The monthly limit per profile stops one client from using it all.

Can end customers log in themselves?

The dashboard is for your company and the people you invite. End customers use your product, and you show them what they need from the API.

Can a profile have its own number?

Yes. Each profile can have its own SMS number and its own phone numbers, sender names and letterhead.

Can we get our own prices?

Yes. A company can have its own price list. Get in touch and we will look at your volume.

Read more about the services

Set up your first client

Register your company, create a company key with profiles:manage, and create the first profile from your system.