Developer overview

Welcome to the technical half of the docs. This section gives you two tracks:

• Global architecture & APIs – how the edge service, routing rules, health probes, and credentials behave.
• Platform SDKs – per-platform setup plus deeper reference material.

Use the map below to decide where to jump next.

How to use this section efficiently

If you are integrating LinkMe into an existing app stack, start with authentication and endpoint behavior before you touch SDK code. That gives you a clear contract for keys, scopes, error handling, and routing outcomes. Once that baseline is clear, move into platform setup for iOS, Android, or cross-platform runtimes.

If you are migrating from another deep linking provider, treat the docs as a cutover checklist:

1. Validate endpoint and key model in REST Endpoints & OpenAPI.
2. Confirm route and fallback semantics with API Keys & Authentication.
3. Configure platform-specific SDK setup in /developer/setup.
4. Add event delivery checks in Webhooks API.
5. Run parity QA on click, open, and deferred flows before traffic migration.

Architecture & APIs

• Architecture diagrams – available from support upon request for security and compliance reviews.
• Link routing & QR behavior – see REST Endpoints & OpenAPI for platform detection, debug tooling, and passthrough semantics.
• /api/health contract – documented inside the REST Endpoints & OpenAPI spec.
• REST Endpoints & OpenAPI – download the public spec or explore Swagger UI.
• API Keys & Authentication – header formats, capability flags, and rotation tips.
• MCP Security & Access Model – guardrails that ensure MCP cannot exceed REST permissions.
• Webhooks API – event types, delivery behavior, retries, signatures, and portal management.

Platform setup & SDKs

• Developer Setup Hub – pick iOS, Android, React Native, Flutter, Web, or Node quickstarts.
• Android SDK
• iOS SDK
• React Native SDK
• Flutter SDK
• Web SDK
• Node SDK

Each SDK page includes installation, initialization, listeners, deferred link handling, and analytics helpers.

Recommended integration sequence

To reduce rollout risk, use the same sequence across all platforms:

• Configure app identity and domain association details.
• Add SDK initialization and listener handling.
• Test direct opens, deferred opens, and fallback behavior on real devices.
• Validate attribution fields and event payload shape.
• Enable webhook delivery only after the core routing paths are stable.

Following this order prevents a common failure mode where teams debug analytics or webhook behavior before confirming that base link resolution is correct.

Bookmark this page whenever you need orientation between higher-level concepts and SDK-specific deep dives.