For developers
Links as an API primitive
Treat short links like any other resource in your stack: created by your backend, updated by your CMS, measured through your dashboards — all over a typed REST API.
An API you don't have to babysit
Scoped keys limit blast radius, idempotency keys make retries safe, cursor pagination behaves at any scale, and every error carries a machine-readable code plus a request ID. The OpenAPI document is generated from the same schemas that validate requests, so it can't lie.
- Bearer keys with granular scopes, hashed at rest
- Idempotency-Key support on all creates
- Consistent error envelope with request IDs
- OpenAPI 3 spec at /api/v1/openapi.json
Event-driven by design
HMAC-signed webhooks for link and billing events, delivery logs with replay, and a conversion-event ingestion endpoint let you wire EndURL into pipelines instead of polling it.
Frequently asked questions
Are there official SDKs?
The API contract is SDK-stable and OpenAPI-typed; official JavaScript, Node and Python packages are planned, and the spec generates clean clients today.
How are API keys secured?
Only SHA-256 hashes are stored; verification is constant-time; keys support scopes, expiry, rotation and instant revocation, with every use auditable.