Nimriz
SaaS & developers

API & workflow automation

Teams that ship campaigns at scale need links created by scripts, CRMs, or internal tools. Nimriz exposes a server-side API for predictable link operations so your automation code stays lightweight.

  • Create, check, and update short links via HTTPS API — retry-safe and idempotent
  • Slug policies and destination validation enforced server-side, not in your automation code
  • Domain-bound operations — automation for one client domain never touches another
Start for freeAll use cases
API automation flow

A three-step pattern: preflight, create, store. Safe to retry at every step.

Server-side
1
Check slug availability
POST /api/check-slug
{ domain_id: "…", slug: "spring-launch" }
→ { available: true }
2
Create the link
POST /api/shorten
{ domain_id: "…", long_url: "https://…", custom_slug: "spring-launch" }
→ { short_url: "https://brand-a.to/spring-launch" }
3
Store result
→ short_url → persisted in your CRM or database

What you get

HTTPS automation endpoints

Create links, check slugs, and update expirations through API endpoints built for retries and idempotent workflows.

Policy-aware server side

Slug conventions, destination validation, and domain rules enforced server-side — clients stay lightweight.

Bulk link creation

Generate hundreds of links programmatically from product catalogs, campaign matrixes, or partner lists.

Lifecycle management

Update destinations, rotate slugs, and set or extend expiration dates without taking links offline.

How it works

Build once, create links everywhere

A three-step automation pattern: preflight slug availability, create the link, store the result. Each step is safe to retry. All policy enforcement happens on the server — your client code stays thin.

1
Plan

Create a short URL (POST /api/shorten) with optional custom slug, expiration date, and redirect type.

2
Publish

Preflight slug availability (POST /api/check-slug) before creating — useful for deterministic slug workflows.

3
Measure

Update expiration (PUT /api/update-expiration) and slug (PUT /api/update-slug) without taking links offline.

  • Destination safety rules — blocked schemes and loop prevention — enforced centrally, not in automation code.
  • Use workspace API keys scoped to specific operations — keep privileged credentials out of client-side or edge code.
  • All API operations are domain-bound — automation for one client domain never affects another from the same workspace.
API & automation featuresTrust & privacyFAQ
Example
On deal created in CRM
1. POST /api/check-slug → confirm slug is free
2. POST /api/shorten with deal ID as custom slug
3. Store short_url on the contact record
4. Include short_url in outbound email template
Result
https://rix.to/deal-4872 → personalized landing page

Related use cases

Smart routing & experimentation
Combine automation with routing rules.
Multi-brand operations
Automate links across client domains.
Conversion tracking
Track outcomes on automated links.

Ready to get started?

Create your account and start using Nimriz in minutes. Starter is free — no credit card required.

Start for freeView pricing