LinkForge
Developer API

Programmatic Link API & Conversions Webhooks

Integrate branded link creation, dynamic QR generation, and conversion attribution directly into your SaaS product, mobile app, or internal toolchain.

Developer Infrastructure

Built for serverless workloads and modern web stacks

Clean JSON payloads, fast response times, and real-time webhook events for developer workflows.

RESTful Link Endpoints

Create, update, archive, and query short links programmatically with standard REST endpoints and JSON schema validation.

Conversions API

Post server-to-server conversion events to tie revenue and user signups back to specific campaign link clicks.

Real-Time Webhooks

Receive signature-verified webhook notifications when links get clicked, thresholds trigger, or domains complete verification.

Simple, Reliable SDK & API Integration

Whether you're automating SMS marketing links, generating QR codes in PDF invoices, or building custom client portals, LinkForge APIs make short link automation straightforward.

  • Bearer token authentication with scoped workspace permissions
  • Predictable rate limiting and clear HTTP status error codes
  • Interactive API sandbox in LinkForge documentation
// POST /api/v1/links
curl -X POST https://linkforge.site/api/v1/links \
-H "Authorization: Bearer lf_sec_..." \
-H "Content-Type: application/json" \
-d {
"url": "https://example.com/promo",
"domain": "go.yourbrand.com",
"utm_source": "newsletter"
}

FAQ

Frequently Asked Questions

Common questions about LinkForge API and developer tooling.

How do API key permissions work?

API keys inherit scoped workspace permissions, allowing developers to generate read-only keys for reporting or write keys for link generation.

How does the Conversions API record attribution?

Developers post conversion payloads (event_name, order_value, transaction_id) to `/api/v1/conversions` referencing the visitor click token.

Are rate limits enforced on API endpoints?

Yes. LinkForge enforces predictable tier-based rate limits with standard HTTP 429 response headers and burst allowances for high-volume apps.