Workspace API keys
Supported API routes can be called from trusted backends without exposing server credentials in the browser.
Automation & attribution
Conversion tracking and campaign automation
Use workspace API keys, bulk flows, UTM metadata, conversion callbacks, destination history, and signed webhooks to automate link operations.
What teams get
- Create and manage links from your own backend with workspace API keys and bulk-friendly flows.
- Keep campaign metadata structured with UTM presets, tags, and spaces instead of hiding everything in the raw destination URL.
- Use signed webhooks and conversion callbacks so downstream systems can react to the same canonical link events.
Availability
Available on supported plans
Core automation is available today on supported plans; webhooks, conversion tracking, and some reporting depend on your plan. Finer-grained query forwarding is planned.
Campaign metadata that stays structured
UTM presets, tags, and spaces give teams a reusable model for attribution and reporting instead of one-off query-string edits.
Destination history and rollback
Edit link destinations with history, restore previous states deliberately, and keep retargeting changes auditable.
Signed events and callbacks
Webhooks and conversion tracking make Nimriz usable inside server-side automation, partner attribution, and CRM or warehouse flows.
One automation loop, end to end
A growth team can standardize destination metadata, create the link programmatically, watch for lifecycle events, and record downstream outcomes.
Provision
Check slug availability, then create the short link with campaign metadata.
Organize
Attach tags, spaces, and reusable UTM presets for cleaner reporting later.
React
Receive signed webhook events for changes that matter operationally.
Measure
Send conversion callbacks back to Nimriz for privacy-safe downstream outcome reporting.
Why this is bigger than an API checkbox
- Automation only works well when API credentials, audit posture, and campaign metadata all share the same operational model.
- Destination history matters because real campaigns change after launch and teams need rollback, not just blind edits.
- Webhooks and conversions let Nimriz fit into broader stacks without requiring a browser pixel today.
- By keeping metadata structured, the reporting layer does not collapse into whatever happened to be in the latest destination URL.