Vai al contenuto
CLUP.life
Indice della documentazione

Developer documentation: API, webhooks and MCP

Connect CLUP.life to your website, calendar, automation and AI assistants: REST API, signed webhooks and MCP server. Your first call in 5 minutes.

La documentazione tecnica è disponibile in tedesco e inglese; nella tua lingua mostriamo la versione inglese.

Clubs, associations and municipalities do not work in CLUP.life alone. They have a website, a calendar, a spreadsheet, maybe an automation or an AI assistant. The CLUP.life interfaces connect those tools to your data — with the same rights you have in the app, and with data protection as the foundation.

The building blocks#

Building blockWhat forTier
REST API v1Read events, posts, announcements, tasks and members; create events, announcements and tasksReading: Basic · Writing: Premium
Exports (iCal, CSV, JSON)Events in your calendar, lists in Excel or Google SheetsBasic
WebhooksReport events (“new event”) to Zapier, Make, n8n or your own serverPremium
MCP serverLet AI assistants (e.g. Claude) answer “What is on this week?”Reading: Basic · Writing: Premium

Your first call in 5 minutes#

  1. Sign up or sign in — register for free. Only adult accounts can create keys.
  2. Create a key: in the app under Settings → Interfaces, enter a name, pick only the scopes you need (to start: profile:read and events:read), choose the validity and click Create key.
  3. Copy the key immediately. It is shown only once; we store only a checksum. Keep it in an environment variable, never in source code.
  4. Send your first call (see below). A 200 response with your name means everything works.
  5. Next: fetch events, copy examples, try it in the console or set up a webhook.

GET/ext/me

Who am I? Account, scopes of the key, memberships

Aree: profile:read

curl -H "Authorization: Bearer clup_k_…" \
  "https://api.clup.life/api/v1/ext/me"

The response contains your account, the scopes of the key and your memberships with the slug of each organization. You need that slug for all further calls.

{
  "id": "u_8f3k2…",
  "displayName": "Mira Muster",
  "organizationKey": false,
  "scopes": ["profile:read", "events:read"],
  "memberships": [
    { "organization": { "slug": "tus-musterstadt", "name": "TuS Musterstadt", "type": "CLUB" }, "role": "MEMBER" }
  ]
}

Base URL and format#

  • Base URL: https://api.clup.life/api/v1 (local: http://localhost:4000/api/v1). All paths in the reference start with /ext.
  • All calls over HTTPS only, with the header Authorization: Bearer clup_k_….
  • Responses are JSON (UTF-8); exports return text/calendar or text/csv. Times are ISO 8601.
  • Lists are cursor pages: items and nextCursor; append ?cursor=<nextCursor> until it is null. There is no OFFSET.
  • Errors always carry a stable code and a readable message (see limits and error codes).

API status#

Verifica dell’API in corso …

Where to go next#

Developer documentation: API, webhooks and MCP · CLUP.life