Workspace API keys
Supported API routes can be called from trusted backends without exposing server credentials in the browser.
Automation & APIPlus+, depth varies
API, webhooks, and workflow automation
Create and manage links from your backend with workspace API keys, keep campaign metadata structured with UTM presets, and use signed webhooks to connect Nimriz to downstream workflows.
API keys
Workspace-scoped
Signed
Webhook delivery
Reusable
Metadata model
app.nimriz.com · API & webhooks
POST /api/v1/links
Workspace API key · created from your backend
Create link · request body
slug free
{
“destination”: “brand.com/launch”,
“slug”: “launch-q2”,
“utm_preset”: “email-spring”,
“tags”: [“q2”, “email”]
}
fires on link.clicked · link.converted
link.clicked
🇺🇸 US · Instagram · mobile
Signed webhook · POST /hooks
sending
{
“event”: “link.clicked”,
“slug”: “launch-q2”,
“country”: “US”,
“signature”: sha256=8f3c…a91
}
Signature verified before your workflow runs
Workflow automationno polling
Slack
Posted to #growth-alerts
CRM
Contact timeline updated
Warehouse
Event row appended
Without a dedicated link workflow
- Configuration, reporting, and follow-up work can spread across multiple tools.
- Teams rely on manual notes or separate dashboards to explain what happened.
- Changing campaign behavior often requires recreating or replacing links.
With API & automation
- The capability stays attached to the same branded short-link record.
- Operational details are easier to review alongside analytics and related links.
- Teams can keep the public URL stable while improving how the link behaves behind it.
What you 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 destination URL.
- Use signed webhooks so downstream systems can react to the same canonical link events without polling the dashboard.
Availability
UTM presets start on Plus. Tags, spaces, destination history, and bulk import unlock on higher tiers.
Lifecycle webhooks, signed Conversion API requests, and QR API endpoints are Professional+. Workspace API keys follow your plan entitlements.
How it works
1
Provision an API key for your backend
Create a workspace API key scoped to the operations your backend needs. Use it from CRMs, internal tools, or data pipelines without exposing credentials in the browser.
2
Structure metadata at creation time
Attach UTM presets, tags, and spaces when creating links programmatically. Consistent metadata at creation time means your reporting layer does not need to reverse-engineer intent from raw destination URLs.
3
React to lifecycle events with signed webhooks
Subscribe to link lifecycle events. Signed webhook payloads let your downstream systems react to changes without polling or screen-scraping dashboard state.
Everything included
Delivery you can watch
Outbound delivery stays async and privacy-aware, with destination-specific redaction, queue-backed retries, and dashboard-visible health signals.
Signed payloadsQueue-backed retriesPer-feed filtersRedaction
app.nimriz.com/integrations
Delivery success · 24h
99.2%
Google Analytics 4
Analytics · default mapping + overrides
Segment
CDP · default mapping + overrides
Meta CAPI
Ads · default mapping + overrides
Generic HTTP
Webhook · default mapping + overrides
Delivery queue
GA4 payload204
Segment track200
Meta retry+60s
Structured campaign metadata
UTM presets, tags, and spaces give teams a reusable model for attribution and reporting instead of one-off query-string edits on every link.
Destination history and rollback
Edit link destinations with a full history. Restore previous states deliberately and keep retargeting changes auditable.
Signed webhooks
Webhook payloads are signed so downstream systems can verify authenticity without trusting unverified event sources.
Conversion API
Send conversion outcomes back to Nimriz for privacy-aware downstream attribution, useful for server-side CRM and warehouse flows that need the click-to-conversion chain.
Slug availability check
Check slug availability before creation to avoid silent overwrites or unexpected conflicts in high-volume programmatic workflows.
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 API requests back to Nimriz for privacy-aware downstream outcome reporting.
Click to conversion · one canonical link
Short-link click
go.brand.com/launch-q2
Conversion API request
Signed, server-side
Outcome attributed
Sale · €129 · launch-q2
Privacy-aware. Outcomes survive blocked pixels and stay on the originating short-link record.
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.
Related next steps
Ready to try it?
API & automation is available on supported plans
Create an account to explore Nimriz, then use pricing to choose the plan and setup path that matches this workflow.