All features
Track & understand
Copy tracking Copy history Custom catalogues NEW Collection insights
Own & collaborate
Data ownership Collaboration Organization Photos & browsing
Protect & extend
Protection & care API Self-hosting Security
Pricing Docs API FAQ GitHub Sign in

For people who look at a catalogue and think “API”

Your collection can leave the app. Politely.

KolleK has a documented JSON API for the people who want their collection to connect to a script, a dashboard, an import process of their own, or something wonderfully specific.

Open the toolbox

Getting started

Introduction

Authentication

Pagination

Rate limits

Resources

GET List items
GET Get item
POST Create item
GET List collections
GET List locations
GET List collection types
GET /api/items GENERATED FROM SOURCE

List items

Retrieve items across every collection, or scope the list to one collection with the collection query parameter. Returns a paginated list of item objects.

Query parameters

collection string optional
per_page integer optional
page integer optional

Personal API keys

The same catalogue, available to your tools.

Use a personal API key to read and manage the collection through straightforward HTTP requests. Collections, items, copies, history, locations, and the rest are not trapped behind the interface.

collections items copies history locations item-types
Create API key Settings · Developer

Name

Household dashboard sync
Your new key Copy

14|aB3cD4eF5gH6iJ7kL8mN9oP0qR1sT2uV3wX4yZ5aK

Copy it now. This is the only time the full key will be shown.

Reference

Documentation that comes from the product.

The API reference is generated from the codebase. That means the endpoint documentation is built to stay close to what the app actually supports, rather than drifting into archaeological fiction.

cURL JavaScript PHP Request
curl https://kollek.example/api/items \
-H "Authorization: Bearer $KOLLEK_KEY" \
-G --data-urlencode "collection=17" \
--data-urlencode "per_page=2"
200 OK Response · application/json
{
"data": [
{ "id": 512,
"name": "Kind of Blue",
"location": "Shelf B2" }
],
"links": { "next": "…?page=2" },
"meta": { "current_page": 1, "total": 128 }
}
Page-based pagination (links + meta) 60 requests / min per user Bearer-token authentication

Interoperability

An escape hatch, on purpose.

Need to analyse your catalogue elsewhere? Build a private report? Move information into another workflow? The API gives you a clean route out without making the product less useful inside.

KolleK API

kollek.app/api

Your catalogue

A private script

Read the catalogue on a schedule and do something specific with it.

Your own dashboard

Pull items and locations into a view you built yourself.

A spreadsheet

Export a slice of the collection when another tool needs the data.

Webhooks

Webhooks: honest status report.

You can register signed webhook endpoints today. Product events do not trigger deliveries yet. We are not going to call that “coming soon” and hope you infer the rest.

Webhook endpoints 1 registered
https://hooks.mydash.io/kollek Idle
Signing secret whsec_••••••8d2f
Signature scheme HMAC-SHA256
Deliveries 0
Endpoint registration and signing work now. No product event fires a delivery yet, so this endpoint will stay idle until it does.

Read the reference. Build the thing you actually wanted.

Endpoints, authentication, pagination, and rate limits, generated from the codebase and ready for your key.

Explore the API reference

KolleK might not be for you (yet) if…

You need turnkey integrations with every service under the sun.

You need event-driven webhooks today. Endpoints and signing exist, but no product event fires them yet.

Choose KolleK when…

You want a documented JSON API for your own tools and scripts.

You need direct, token-authenticated access to the catalogue now.

We will update this page when the product changes. The feature status page has the boring-but-important details.