API or connector?
linkable.id offers two ways in from outside the panel. They solve different problems.
| Public API | Claude connector | |
|---|---|---|
| For | Your own systems: a CRM, a campaign tool, a script | Working with Claude in chat, Cowork or Claude Code |
| Covers | Short links, their QR codes and link stats | Most of the panel: links, pages and widgets, sites, themes and custom CSS, the Brand Vault, Custom Pages, design systems and team cards |
| Signs in with | An API token you create, for one workspace | Your linkable.id sign-in, approved on a consent screen, for one workspace |
| Acts as | The token's owner, within the permissions you give the token and their role | The person who connected it, with their role |
| Limits | A rate limit per token and a monthly API calls limit on your plan | A rate limit per connection; your plan's limits |
| Availability | Plans that include the API | Plans that include the AI connector |
Which one
- Choose the API when a system should create links without a person: a form that issues a tracked link per campaign, a nightly job that reads click stats.
- Choose the connector when a person wants to get work done by asking: build a page, restyle a theme, fill the vault, import people.
- Both keep your role's limits and the plan's, and record what they do in the activity log.
Neither one deletes anything: deleting stays in the panel.
With Claude
Claude uses the connector, never the API. See Connect Claude to set it up, and the connector reference for every tool.