API & developers

Export click data

Dashboards are for glancing; exports are for owning your data. The visits endpoint hands you every recorded click so you can analyze it your way.

Pulling raw visits

Pull raw visits for any of your links:

GET https://goto.now/rest/v3/short-urls/{shortCode}/visits
Header: X-Api-Key: YOUR_KEY

Each visit row carries:

• The timestamp.
• The referrer.
• The user agent.
• Coarse location.

Paginated, ready for your warehouse. Page through until you've drained the history, load it into your database, and schedule the pull nightly so the warehouse stays current.

Joining clicks to outcomes

Join it against orders or signups and you own your attribution model instead of renting a dashboard. A concrete recipe: create one short link per campaign, store each link's shortCode next to the campaign record, then join visit timestamps against order timestamps within your chosen window. Now "did the March newsletter drive sales?" is a SQL query on your own data, not a guess.

When you only need totals

Aggregate summaries are also available per link for quick totals - The right tool when a nightly job just needs "clicks per link" for a report card, without shuttling thousands of raw rows around. Use raw visits for analysis, aggregates for monitoring.

A practical pattern: run the aggregate call hourly to power a live dashboard tile, and the full raw pull once a night for the warehouse. You get fresh numbers all day without hammering the paginated endpoint.

Remember these numbers are private to your API key's account, same as the dashboard - Exporting doesn't make them public, it just moves your own data into your own hands.