What developer resources does s.id provide for integrating links and QR codes?
s.id publishes developer documentation for teams that want to connect short links, QR codes, and campaign pages to their own stack. The documented resources cover an API reference, an authentication flow, webhooks, and an MCP guide, and they are collected under the developer docs section of the site. If your integration only needs to create links by hand in the dashboard, you do not need these; if you want link creation, destination updates, or performance data to run inside your own product or automation, start with the API reference and authentication flow.
What the developer documentation covers
The site states that you can "review the API reference, authentication flow, webhooks, and MCP guide before you connect s.id to your stack." Each of these serves a different integration pattern:
| Resource | What it is for | When you need it |
|---|---|---|
| API reference | Programmatic access to create and manage links, QR codes, and related objects | Building link creation into your app, CMS, or internal tooling |
| Authentication flow | How your client proves identity to the API | Any server-to-server or app integration |
| Webhooks | Event notifications pushed to your endpoint | Reacting to clicks or link events without polling |
| MCP guide | Connecting s.id to MCP-based tooling | Wiring s.id into an AI assistant or agent workflow |
The MCP guide is the least common of the four in link-management products, so it is worth checking first if your goal is to let an assistant or agent create and manage links on your behalf.
Where to find it
The developer docs are linked from the product site under the section that describes "the product, policies, and paths behind every link." The page presents this as a deliberate alternative to placeholder metrics or unverified claims, so expect reference material rather than marketing summaries. Start at the developer docs entry point on home.s.id and follow the API reference from there.
How to approach an integration
- Confirm your use case fits the API. Decide whether you need to create links, update destinations, read analytics, or receive events. The API reference is the source of truth for which of these are exposed.
- Read the authentication flow before writing code. Authentication determines how you store credentials and how requests are signed or authorized. Getting this wrong is the most common reason a first API call fails.
- Prototype one call end to end. Create a single short link through the API and resolve it in a browser. This verifies credentials, request shape, and the returned link in one pass.
- Add webhooks only if you need push events. If your workflow can tolerate polling the analytics endpoints, you can defer webhooks and reduce the surface area of your first release.
- Check plan eligibility for what you build. The site notes that "eligible plans also support custom domains and higher usage limits." If your integration depends on a custom domain or high request volume, verify that your plan includes it before you build around it.
Common sticking points
- Custom domains and usage limits are plan-dependent. The documentation describes the capability, but availability depends on your subscription. Check the subscription page rather than assuming the API exposes everything on every plan.
- Webhooks need a reachable endpoint. If your environment cannot accept inbound HTTPS requests, plan for polling instead.
- MCP is for tool-based workflows, not general scripting. Use the API for conventional integrations and the MCP guide when you are connecting s.id to an assistant or agent.
- Analytics data availability may vary. The platform advertises click, location, device, and referrer data; confirm which fields the API returns for your plan before designing dashboards around them.
What to check before you commit
Read the API reference and authentication flow first, since they determine whether your intended integration is feasible at all. Then confirm plan eligibility for custom domains and usage limits, because those are the two constraints most likely to force a redesign. Webhooks and the MCP guide are additive — you can adopt them after a basic API integration works.