JaKun API

Connect your systems to JaKun CRM: REST for records, MCP for AI agents, signed inbound events and outgoing webhooks.

Every JaKun tenant gets its API from its own metadata. Add a field or install a pack, and the endpoints, validation and MCP tools follow — no new code, no new version to wait for.

Quickstart#

  1. Create a key. In JaKun, go to Indstillinger → API and press New key. Name it after the sending system (for example cbot). Copy the .env block — the token and the signing secret are shown once.
  2. Call the API. Read the objects of your tenant:
    curl https://jakun.dk/api/v1/meta/objects \
      -H "Authorization: Bearer $JAKUN_TOKEN"
    import os, httpx
    
    r = httpx.get("https://jakun.dk/api/v1/meta/objects",
                  headers={"Authorization": f"Bearer {os.environ['JAKUN_TOKEN']}"})
    r.raise_for_status()
    print([o["name"] for o in r.json()["data"]])
    const r = await fetch("https://jakun.dk/api/v1/meta/objects", {
      headers: { Authorization: `Bearer ${process.env.JAKUN_TOKEN}` },
    });
    if (!r.ok) throw new Error((await r.json()).error.code);
    console.log((await r.json()).data.map((o) => o.name));
  3. Send a test event. In Indstillinger → Forbindelser press Test event next to your product, or send one yourself — see Send an event.
  4. Check the journal. Indstillinger → Hændelseslog shows every event with its result. In dry_run nothing is written to the CRM; the response shows what would happen.
  5. Go live. Switch the key to live when the journal looks right.

Base URL and versioning#

All endpoints live under https://jakun.dk/api/v1. Changes inside v1 are additive: new fields and endpoints may appear, existing ones keep their meaning. Anything that could break a client is announced in the changelog first.

Test mode is a key setting#

Instead of separate test and live keys, every key has a mode. A new key starts in dry_run: inbound events run through the real handler inside a savepoint that is rolled back, and MCP writes default to dry_run=true. You see the exact result, and customers never get a message from a test.

What JaKun does not do#

  • It never sends SMS, email or WhatsApp to customers by itself from an API call: send_message only queues a message, and delivery to real customers is switched on by the tenant owner.
  • Integration keys can't export the tenant, manage users, keys or webhooks.