REST API
Use the REST API for server-side automation or platforms that do not yet have an SDK.
Integration options
Official SDKs (recommended)
Whenever possible, use the native SDKs so installation tracking, session management, and retries happen automatically:
Direct API integration
If you are building a backend service or unsupported client, follow the Direct Integration Guide.
Quick reference
The typed OpenAPI 3.1 specification is available at
https://ulink.ly/openapi.json for agents,
client generators, and function-calling integrations.
Authentication
X-App-Key: your-api-key
Content-Type: application/json
Base URL
https://api.ulink.ly/v1
Core endpoints
| Endpoint | Purpose |
|---|---|
POST /sdk/installations/track | Track app installations |
POST /sdk/sessions/start | Start a session |
POST /sdk/sessions/{id}/end | End a session |
POST /sdk/links | Create dynamic/unified links |
GET /sdk/resolve?url=… | Resolve link data |
A link's QR image is also served from a public, no-auth URL you can embed anywhere — see QR Codes.
API key
Create or rotate keys under Dashboard → API Keys. Store them in your backend only.
Use the /v1 base for all new integrations. The unversioned base is deprecated but remains compatible; see Versioning and Deprecation.
Runtime contract
- Versioning and Deprecation explains major versions plus
Deprecation,Sunset, and lifecycle links. - Rate Limits documents live
RateLimitfeedback andRetry-Afteron 429. - Typed Errors defines the RFC 9457
application/problem+jsonmodel and stable error codes.
Query-parameter passthrough
Dynamic links accept an optional allowQueryPassthrough boolean field (default false). When enabled, query params appended to the live link URL are merged into the resolved parameters map delivered to the app, overriding any stored param with the same key. Values always arrive as strings.
See the Query-Parameter Passthrough guide for the full field reference, validation limits, and examples.
Next steps
- Read the Direct Integration Guide for full request/response examples.
- Implement installation tracking and session management first; other endpoints depend on that context.