Build on the Kelynto partner API.

One partner key. One workspace per client. Send a client's files, produce and read its weekly review, download it as a document, show it inside your application, and receive a signed webhook when something happens.

From a key to a published review, in six requests.

The sandbox holds two synthetic client workspaces. Every request works the same way against your real clients with your real key.

  1. See who the key is

    curl -s "$KELYNTO_URL/api/partner/v1" -H "Authorization: Bearer $KELYNTO_PARTNER_KEY"
  2. List your clients, each with its summary line

    curl -s "$KELYNTO_URL/api/partner/v1/clients" -H "Authorization: Bearer $KELYNTO_PARTNER_KEY"
  3. Send a file

    curl -s -X POST "$KELYNTO_URL/api/partner/v1/clients/$CLIENT/data/stores" \
         -H "Authorization: Bearer $KELYNTO_PARTNER_KEY" -H "Idempotency-Key: stores-2026-w43" \
         -F "file=@stores.csv"
  4. Produce the review

    curl -s -X POST "$KELYNTO_URL/api/partner/v1/clients/$CLIENT/runs" \
         -H "Authorization: Bearer $KELYNTO_PARTNER_KEY" -H "Idempotency-Key: run-$CLIENT-w43" \
         -H "Content-Type: application/json" -d '{"week_start": "2026-10-19", "force": true}'
  5. Publish it

    curl -s -X POST "$KELYNTO_URL/api/partner/v1/clients/$CLIENT/reviews/2026-10-19/publish" \
         -H "Authorization: Bearer $KELYNTO_PARTNER_KEY" -H "Idempotency-Key: publish-$CLIENT-w43"
  6. Download it as a document

    curl -s -o review.pptx "$KELYNTO_URL/api/partner/v1/clients/$CLIENT/reviews/2026-10-19/document/pptx" \
         -H "Authorization: Bearer $KELYNTO_PARTNER_KEY"

The full quickstart, with Python beside curl and what each answer holds.

What the API covers.

Every route is versioned at /api/partner/v1. A change that would break a caller comes as a new version.

GroupWhat it doesScope
ClientsList your clients with their summary lines, make a client workspace, read one client.clients:read, clients:write
DataSend a client's files through the same validation, delivery gate, control totals and loader as every upload. Read what became of a file, and the client's data health.data:write, data:read
ReviewsProduce a client's weekly review, read it and its findings with their evidence, and publish it where the client allows it.runs:write, results:read, reviews:publish
DocumentsThe review of a week as a Word document, a PDF or a PowerPoint deck, rendered on the server.results:read
Outlook and summaryThe weeks ahead by cause beside the client's plan or forecast, and the client's summary line as it stands now.results:read
WebhooksAdd, change, test and remove a client's webhooks, read the delivery log, and send a delivery again.webhooks:manage
EmbeddingMint a single-use embed token for one person and one client, and end embedded sessions.embed:create
Licenses and usageYour pool of client licenses and each client's tier, and usage per client and month.clients:read

Every route, scope and error code.

Conventions an engineer asks about.

  • Keys. A partner key starts with kpk_, is shown once, holds the scopes chosen for it, expires in 90 days by default, rotates with an overlap, and is revoked at once.
  • Safe retries. Send an Idempotency-Key with every POST. The same key and the same request return the first answer again.
  • Errors a program can read. A refusal answers {"error": {"code", "message", "status"}}, with the code in the X-Error-Code header too.
  • Rate limits. Requests are limited per key, and a 429 carries Retry-After.
  • Files. 201 loaded, 202 held for a decision, 200 received before, 422 refused with a report and a problem file by row and column.

Webhooks.

  • Events. A file loaded or held, a review produced or published, an Outlook issued, the Monday pack sent, and a license pool running low.
  • Signed. Each delivery carries an HMAC-SHA256 signature with a secret of its own, and a timestamp to refuse a replay.
  • Retried and logged. Six attempts with backoff, a delivery log, a test delivery on request, and replay of any delivery with the same body and id.

The receiver's verification function.

Embedding.

Your server mints a token for one person and one client. Your page puts the address it gets in an iframe.

  • Four views. The weekly review, the causes with their evidence, the Outlook and This quarter.
  • Single use, minutes long. A token is bound to one person, one client and one of your origins, and works once.
  • Cookie or header. The session travels in a partitioned cookie, or in the page's memory for browsers that block framed cookies.
  • Your brand. Your name, logo and color in the frame, on the documents and on the mail.

The embedding guide, with the messages between the frame and your page.

<iframe id="kelynto" title="Weekly review" src="{{ embed_url }}"
        referrerpolicy="origin"></iframe>
<script>
  window.addEventListener('message', (event) => {
    if (event.origin !== KELYNTO) return;
    const m = event.data || {};
    if (m.type === 'resize') frame.style.height = m.height + 'px';
    if (m.type === 'session-ended') location.reload();
  });
</script>

A minimal page, served from your embed origin. The full example is in the embedding guide.

Isolation and audit.

  • One workspace per call Kelynto looks the client up among your own clients and binds the request to that one workspace, under row-level security in the database.
  • Not found means not yours A client that is not one of your clients answers 404, whether the workspace exists or not.
  • On the client's record Every request with your key is in the client's audit log, with the key as the actor.
  • Scopes that change what a client sees are opt-in Producing a review, publishing it and minting embed tokens are given to a key only when asked for.

Tenant isolation in the Trust center, and the security overview for your reviewer.

Request sandbox access.

You receive a base address and a sandbox key that reaches two synthetic client workspaces for 30 days, and the synthetic clients the key makes itself. Every name in the sandbox is marked synthetic.

  • What to send. Your company, your name and role, and the origin of the page you will embed from, if you plan to embed.
  • What you can do. Every route of the API with every scope, the embedded views in your own page, and webhooks to a receiver of yours.

Two ways to ask

  • Write with the subject "Sandbox access" and the three facts on the left
  • Or book a conversation and get the key in it, with a walk through the partner console
Email marc@kelynto.com

Book a 30-minute partner conversation