API automation

Teams that ship campaigns at scale often need links created by scripts, CRMs, or internal tools. Nimriz exposes a small server-side API for predictable link operations—without embedding privileged credentials in clients.

Automation endpoints

Create links, check slug availability, and update expirations through HTTPS APIs designed for automation and retries.

Policy-aware behavior

Slug policies, destination validation, and domain rules are enforced server-side so clients remain lightweight.

Real example

A typical automation flow is: check slug availability → create link → store the returned short URL in your system.

1) Check slug
POST /api/check-slug { domain_id: "...", slug: "spring-launch" }
2) Create
POST /api/shorten { domain_id: "...", long_url: "https://example.com/...", custom_slug: "spring-launch" }
3) Result
short_url: https://rix.to/spring-launch

What you can automate today

  • Create a short URL (`POST /api/shorten`) with optional custom slug and expiration.
  • Preflight slug availability (`POST /api/check-slug`) for UI and scripts.
  • Update expiration (`PUT /api/update-expiration`) and slug (`PUT /api/update-slug`).
  • Enforce destination safety rules (blocked schemes, managed-domain loop prevention) centrally.