Linkstacked for developers
Everything in the Linkstacked dashboard is backed by a public-shaped GraphQL API. These pages are written for engineers integrating Linkstacked into their own products, automating profile workflows, or shipping side-by-side analytics dashboards.
Start here
If you've never called the Linkstacked API before, start with Getting started for a 5-minute walk-through that ships a working request.
How the API is shaped
Linkstacked exposes a single GraphQL endpoint at
https://api.linkstacked.com/graphql. Every dashboard surface (profile
authoring, analytics, billing, team, marketplace) goes through the same
endpoint with the same auth model — there is no parallel REST surface to
keep in sync.
- Auth: an OAuth-issued bearer token attached as
Authorization: Bearer <token>. - Versioning: additive only. Field deprecations are surfaced via
GraphQL
@deprecatedand announced in the API changelog. - Rate limits: per-token, per-operation.
X-RateLimit-*headers on every response let you back off proactively.
What you can build today
The API covers the same surface area as the dashboard. The pages below group endpoints by the product surface they belong to:
- Profiles & links — the bread and butter.
- Appearance & themes — branding, fonts, layouts.
- Scheduling & A/B — go-live windows and split tests.
- QR & pixels — permanent QR codes and retargeting hooks.
- Payments & products — tips, digital products, subscriptions.
- Analytics — clicks, conversions, exports.
- Team & imports — roles, SSO, bulk import.
Try it before you build
The GraphQL reference embeds the Apollo Sandbox in non-production environments so you can introspect the schema, run queries against a sample workspace, and copy the request payloads straight into your code.
Need something the API doesn't expose yet?
Public webhooks and user-issued API keys are on the roadmap — the API changelog is the canonical place to track what ships. For everything else, open an issue on GitHub or talk to your account team.