Developer portal

Build on the booking ledger.

Directory access, booking workflow endpoints, and telemetry signals — each contract explicit, each request audited, each key revocable.

Open the quickstart Manage API keys Endpoint reference →

Developer access is available during approved integration onboarding. Endpoints are stable for documented contracts; surfaces marked as preview may change during the founding pilot.

Quickstart

The first authenticated call

Use API keys for server-to-server integrations. OAuth is reserved for future delegated third-party apps. Base URL: https://kalinklo.com

bash

curl -X GET "https://kalinklo.com/api/v1/artists?q=violin&country=Germany" \
  -H "Authorization: Bearer abo_live_your_key" \
  -H "Accept: application/json"

Try it

Sandbox console

Try it out (sandbox)

This console calls a safe mock endpoint and never mutates production data.

Request payloadResponse

// Response appears here

Documentation

Reference chapters

Chapter · 01

Quickstart

API access model, the first authenticated call, and the response envelope you can rely on.

Open chapter

Chapter · 02

Public Endpoints

What can be called without an API key — health, public artist search, and the ICS calendar feed.

Open chapter

Chapter · 03

Auth and Rate Limits

Bearer-token scheme, key lifecycle, rate-limit headers, and retry policy.

Open chapter

Chapter · 04

Telemetry and Status

Request IDs, the error envelope, the HTTP status table, and the health endpoints to monitor.

Open chapter

Chapter · 05

Request Hold widget

Embed a "Request a hold" button on any artist or agency website with one script tag.

Open chapter

SDKs & examples

Reference repositories will be published once the API leaves charter pilot. Use the API docs and sandbox console for current integration behaviour. To request early SDK access, write to the office.