1get gives developers one external surface for branded short links, QR generation, privacy-first analytics, and audit-friendly operations without reusing browser-only dashboard APIs.
Move from product positioning into auth, scopes, response examples, and route behavior.
See the exact request shape, QR payload options, idempotency header, and success contract.
Check which plan unlocks keys, monthly calls, usage visibility, and higher-throughput traffic.
POST /api/v1/links/shorten
Authorization: Bearer 1g_live_...
Idempotency-Key: 6dbf664d-...
{
"original_url": "https://acme.ai/workflows/agent-invite/42",
"custom_slug": "agent-launch",
"qr": { "include": true, "format": "SVG" }
}{
"data": {
"short_url": "https://1get.site/agent-launch",
"qr_code": { "url": "https://1get.site/api/media/qr/..." },
"status": "ACTIVE"
}
}Bearer keys for external systems.
Basic plans can receive a default QR in the shorten response.
Quota and rate limits stay plan-aware from first integration.
API key lifecycle and link mutations belong in one accountable trail.
Use this page to see where 1get belongs in application backends, agents, automations, and internal tooling before moving into full API documentation.
Shorten outbound product links, activation flows, invites, transactional messages, and customer-share surfaces without pushing link creation through browser sessions.
App backend -> 1get API -> short URL + QR -> customer surface
Let AI agents create stable links for generated assets, knowledge packets, campaign outputs, or multi-step workflows while keeping each mutation attributable.
Agent job -> idempotent shorten -> auditable automation log
Use server-to-server requests in Zapier-style flows, growth jobs, queue workers, and partner automations without relying on human dashboard state.
Queue / cron / webhook worker -> scoped key -> machine auth
Give ops, support, and sales tooling a central short-link service with rate limits, org ownership, and usage visibility that survives team changes.
Internal admin tool -> org-scoped key -> managed link infra
The external developer contract is versioned, API-key authenticated, and stable for third-party applications. The dashboard can keep its session-cookie behavior without becoming the public API.
Sign in to manage billing, teams, and API access.
Create or rotate scoped API keys from the dashboard.
See the plaintext key once, then store it in your own secret manager.
Send Authorization: Bearer <api_key> on each external request.
Resolve organization, scopes, and plan entitlements without browser cookies.
Run each request as an API principal bound to the subscribed organization.
Keys resolve organization ownership, scopes, and plan features. They are visible once, stored as hashes, and never carry client-supplied organization context.
POST /api/v1/links/shorten is the main onboarding path.
Return default QR output on create, then unlock richer controls on higher tiers.
Expose GET /api/v1/usage so customers can understand quota and rate behavior.
Help technical buyers and AI systems understand the request shape, auth model, idempotency flow, QR response contract, and likely implementation path in minutes.
curl -X POST https://1get.site/api/v1/links/shorten \
-H "Authorization: Bearer 1g_live_xxxxx" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: 6dbf664d-243e-4e38-8cb2-1a9640f1a1c4" \
-d '{
"original_url": "https://acme.ai/workflows/agent-invite/42",
"custom_slug": "agent-launch",
"utm_source": "copilot",
"utm_medium": "api",
"qr": {
"include": true,
"format": "PNG",
"size": 256
}
}'{
"data": {
"id": "lnk_7z1f2",
"slug": "agent-launch",
"short_url": "https://1get.site/agent-launch",
"original_url": "https://acme.ai/workflows/agent-invite/42",
"status": "ACTIVE",
"created_at": "2026-04-06T09:30:00.000Z",
"qr_code": {
"id": "qr_8ne4c",
"url": "https://1get.site/api/media/qr/qr_8ne4c.png",
"format": "PNG",
"size": 256
}
}
}One write path returns the short URL and default QR together.
Successful shorten requests meter one API call even when QR is included.
Key visibility is one-time at creation; the platform stores only hashed key material.
1get is not a thin wrapper around dashboard routes. Security, privacy posture, and accountability belong in the same operational layer as the API itself.
Built around a fast redirect path so the developer API can support production usage instead of acting like an afterthought.
Useful link analytics without leaning on raw-IP retention as the default operating model.
API key lifecycle events and API-created link mutations belong in the same accountable operational trail.
Keys are shown once, stored as hashes, and resolved to organization ownership instead of being treated as loose personal browser tokens.
The plan ladder climbs from evaluation to production: Basic handles shorten-plus-QR, Business opens broader reads and management operations, and Enterprise adds webhook-heavy, higher-volume control.
Use it to evaluate the product before machine access matters.
Enough for smaller SaaS products, CRMs, no-code tools, and first production automations.
Move from simple shortening to production integrations, analytics reads, and team-scale automation.
Where partner apps, multi-team operations, and webhook-heavy flows belong.
| Route | Basic | Business | Enterprise |
|---|---|---|---|
| POST /api/v1/links/shorten | 60 / min | 300 / min | 1,500 / min or custom |
| GET /api/v1/usage | 30 / min | 120 / min | 300 / min |
| POST /api/v1/links/batch-shorten | not available | 10 / min | 60 / min |
Start with a scoped key and one shorten endpoint, then expand into richer management routes, analytics reads, or Enterprise webhook controls when the integration grows up.
Technical buyers can move from API details into pricing, partner strategy, or the Bitly-alternative comparison without relying only on header and footer navigation.
Positioning, API summary, privacy-first analytics, Bitly-alternative framing, and pricing overview.
Three-column external API reference with quickstart guidance, field-level endpoint docs, cURL examples, and OpenAPI-backed request panels.
Long-form technical guides for Next.js, Python, AI agents, automations, and Bitly migration flows built around the public API surface.
Plan ladder for Free, Basic, Business, and Enterprise with API-adjacent positioning and FAQ.
Partner-program overview for agencies, creators, consultants, and technical partners.
Comparison page for developers evaluating 1get vs Bitly on API approach, speed, privacy, and auditability.
How developers, consultancies, marketing teams, and content creators use 1get — API automation, link analytics, and multi-client workspaces.