Link Management API for Developers

2.9M+

links already in production on the engine behind the API

REST v3

clean JSON endpoints with copy-paste docs on the Developers page

1 header

X-Api-Key is the whole auth story

An API that behaves like infrastructure

Our REST API is boring in the best way: predictable JSON, proper status codes, idempotent creation with findIfExists, tags for organization. It's open source, documented publicly and already battle-tested by our production traffic.

Create, edit, tag, delete via JSON
Idempotent creation for safe retries
Copy-paste docs on the Developers page

Read the API overview

Your click data belongs in your warehouse

The visits endpoints stream every click with timestamp, referrer, user agent and coarse geo. Pipe it into your analytics stack and join link engagement against orders, signups or support tickets - Attribution on your own terms.

Paginated visit exports per link or tag
Referrer, UA and geo on every record
Join click data with your product events

Visits API details

Your click data belongs in your warehouse

QR codes as a URL parameter

GET /{code}/qr-code?size=600&format=svg - That's the whole integration. Generate print-ready codes in CI for packaging runs, render them in dashboards, or attach them to order confirmations without a rendering library in sight.

QR generation via simple GET requests
Size, format and color query params
SVG output for print pipelines

See code samples

We migrated 40k links in via the API in an afternoon. findIfExists made the retry logic trivial.

A typical setupPlatform engineer

More ways Developers teams put GoTo.now to work

REST API v3

JSON in, JSON out. Create, edit, tag and delete short URLs programmatically.

No lock-in

Your full link inventory and click data are exportable through the API at any time - Leaving is always an option, which is why nobody has to.

Own your data

Visits endpoints export every click with referrer, UA and geo for your warehouse.

Automation-ready

Idempotent creation (findIfExists) makes retries and batch jobs safe by default.

FAQs

What's the error format?

RFC-7807 problem JSON: type, title, detail and status on every error, with honest status codes - 400 for bad payloads, 401 for auth, 429 for rate limits.

Is creation idempotent?

Yes - FindIfExists returns the existing link for a repeated longUrl, making retries and batch imports safe by default. Use customSlug with your own IDs for per-entity links.

How do we get click data into our warehouse?

The visits endpoints stream paginated click records with timestamp, referrer, user agent and coarse geo - A nightly pull per tag slots straight into standard ELT.

Where are the API docs?

The Developers page carries the endpoint reference, auth, error format and copy-paste examples - Everything needed to ship an integration.

The developers placement playbook

Where developers teams put their links, what the link looks like, and what the numbers mean once clicks arrive.

Placement	A link that fits	What the numbers tell you
README / docs	`goto.now/api-docs`	Doc entry points by referrer - GitHub vs search vs forums.
CLI help output	`goto.now/cli-auth`	Which help topics users reach from the terminal.
Error payload	`goto.now/err-429`	Rate-limit doc reads that predict support tickets.
Changelog / release notes	`goto.now/v3-breaking`	Whether breaking-change notices got read before the complaints.

Worth knowing: Short links in code comments and error strings outlive repos - Route them all through one account so ownership survives team changes.