Building on the TRIMS API

Everything you can do in the TRIMS dashboard, you can do from your own code. The dashboard is just one client of the same API your integration will use, which means there are no second-class capabilities hiding behind the UI. If you can click it, you can automate it — and for teams that manage links at scale, automation is where the platform earns its keep.

Create and manage links programmatically

The most common starting point is creating links from your own systems. When a user generates content, launches a campaign, or publishes a product, your backend can mint a short link in the same motion — with a custom alias, a destination, tags, and campaign parameters attached. There's no human copying URLs into a dashboard, which means there's no human forgetting to.

The same endpoints let you update destinations, archive links, and organise them into folders. Anything the interface does to a link, the API does too, so a workflow that starts manual can grow into a fully automated pipeline without hitting a wall.

Read analytics into your own tools

Your data belongs to you, and the API makes it portable. You can pull click counts, geographic and device breakdowns, referrers, and time series into your own dashboards, warehouse, or reports. Teams commonly feed TRIMS analytics into an internal metrics view so link performance sits right next to everything else they track.

• Create, update, and archive links with full metadata
• Organise links into folders and apply tags in bulk
• Query click analytics, breakdowns, and time series
• Report conversions server-side for accurate attribution
• Subscribe to webhooks to react to events in realtime

React to events with webhooks

Polling for changes is wasteful and slow. Webhooks flip that around: you tell TRIMS which events you care about, and we post to your endpoint the moment they happen. React to a click, a conversion, or an anomaly in realtime — trigger a workflow, update a record, or fire an alert without ever asking "anything new yet?"

A good API disappears. You stop thinking about the link platform and start thinking about the product you're building on top of it.

Authentication is a straightforward API key, responses are clean JSON, and the endpoints map to the same concepts you already know from the dashboard. Whether you're minting a handful of links or millions, the developer platform is designed to get out of your way. Full details live in the API reference — this is just the map of what's possible.