Skip to content

Developer overview

Studio staff can reach their studio’s data from outside Linyup in two ways:

  • A developer integration, through a versioned REST API.
  • An AI assistant (Claude, ChatGPT, Claude Code and others), through a remote MCP server, so an owner can ask “who hasn’t come in three weeks?” or “how full were Thursday classes last month?”.

Both are the same product: one address (https://api.linyup.com), the same credentials, the same data and permissions. Both are read-only.

Your own website has a third way in: the website data feed shows your public offers, plans and schedule in your site’s design. It uses its own website keys, reads only what your booking page already shows, and comes with the Website add-on on the Studio plan.

API keys need the API & AI connectors add-on. You create them in the app under Settings → API keys. Each key belongs to one studio and carries only the scopes you tick when you create it, plus an optional expiry. The secret is shown once.

Scope Grants
contacts:read Contacts, without personal details
contacts:read:pii Contacts’ personal details (email, phone…)
schedule:read Sessions, rosters, events, a contact’s booking history, class fill rates
offerings:read Activities and plans
subscriptions:read Who holds which plan
reports:read Weekly reports
finance:read Finance reports (needs the Finance add-on)

A key can only use a scope its creator may use in the app: a coach without access to reports cannot read them through the API either. The REST API page lists the scope each endpoint needs.