Link creation and slugs
Create links, choose safe custom slugs, and understand expiration and fallback behavior.
Link creation and slugs
This guide covers the most common link-management tasks: creating a link, choosing a custom slug, and understanding what happens when a link expires.
Create a new link
Before you create a link, decide:
- which domain you want to use
- whether you need a custom slug
- whether the link should expire
- whether the destination URL is final and safe to publish
What makes a good slug
Good slugs are:
- short but still descriptive
- easy to read out loud
- consistent with your campaign naming rules
- long enough to avoid reserved-word conflicts
Avoid:
- spaces
- slashes
- vague one-word slugs that are likely to be reserved or already taken
Reserved and blocked slugs
Some slugs are intentionally unavailable on first-party domains, including platform paths such as admin, api, login, billing, _health, and .well-known.
A slug can also be rejected when it:
- is below the minimum length for that domain or account policy
- was recently cleaned up and is still tombstoned
- is already taken on the same domain
Expiration behavior
Some domains or plans require an expiration time. When a link expires, Nimriz does not continue redirecting to the destination. Instead, the visitor is sent to the configured fallback experience for that domain.
This means an expired link is not the same as a broken redirect target. It is an intentional stop state.
Update a slug or expiration
After a link exists, you can usually:
- change the slug if the new slug is available
- add an expiration time
- extend or remove expiration when your current plan and domain policy allow it
If the product blocks an expiration change, it usually means the new value violates the current policy rather than the link being corrupted.
Common create or edit errors
slug_reserved: the slug is reserved or below the allowed minimum lengthslug_tombstoned: the slug cannot be reused yetdestination_blocked: the destination host or scheme is not allowedinvalid_expires_at: the expiration value is not validmonthly_quota_exceeded: your workspace or public-domain quota has been reached
Tips for fewer support issues
- Keep campaign slugs predictable across teams.
- Use HTTPS destinations by default.
- Test the short link on the exact host before sharing it widely.
- If you change a slug after publishing it externally, remember that the old slug stops working unless you keep both links intentionally.