Error messages
A code printed by a binary shipped two years ago cannot be edited. The page it points at can be, if the address is one you control.
Short links for documentation, releases and tooling
Links in your docs that you can still repoint in five years.
digily.dev · Short links on Digily Link
Documentation outlives the URLs it references. Hosts move, docs sites get rebuilt, and the link you put in an error message in 2024 is dead by 2027. A digily.dev address stays fixed while the destination behind it moves, from the dashboard or from the API.
Example addressdigily.dev/err-401
At a glance
Where a stable short link earns its keep
Documentation
Cross references between docs sites break every rebuild. One indirection layer means one place to fix them.
Release notes
Changelog entries are append only by convention. The links inside them are not, but nobody goes back to fix them.
Printed and embedded
Labels on hardware, QR codes in a manual, addresses in a compiled binary. All read only after the fact.
Digily Link tools
What the link can actually do.
Shortening is trivial. These are the parts that matter when a link has to be maintained rather than just created.
HTTP API
Create, read, update and delete links, projects, QR codes, pixels and statistics with a bearer token. Base URL and endpoints are in the API documentation.
Editable destinations
Repoint any link at any time. Anything already published, printed or compiled in follows without a release.
Readable slugs
Choose the path yourself. digily.dev/err-401 is a reference somebody can type from a terminal; a random code is not.
Routing rules
Resolve by country, device or browser language when regional docs or platform specific downloads differ.
Statistics per link
Requests, countries, devices, browsers and referrers per link, in UTC, without setting anything on the client.
Locks and lifetimes
Passwords, start and expiry dates and click limits, for links attached to a preview, a beta or an embargo.
Two ways in
How do you create a digily.dev link?
The dashboard for one link, the API for the ones your build process should own. Both write to the same account.
By hand
Dashboard
- 1
Create a Digily Link account and open the short link tool.
- 2
Paste the destination and choose digily.dev from the domain list.
- 3
Type the path you want, such as err-401 or install.
- 4
Save, then repoint it whenever the destination moves.
From code
API
- 1
Generate an API key in your account settings.
- 2
Send it as an Authorization bearer header on every request.
- 3
Create or update links against the links endpoint from your release pipeline.
- 4
Read statistics back the same way when you need them somewhere else.
Domain → Digily Link → Resolve
Where does digily.dev actually live?
digily.dev is not a separate service with its own login. It is one of the domains you can pick inside Digily Link when you shorten a URL, build a page or generate a QR code.
The same account holds the links, the routing rules, the codes and the statistics, and the same API key reaches all of them. The full endpoint list, the authentication scheme and the status codes are documented on the Digily Link site.
Take a look at Digily Link9:41
D
digily.devDocumentation linksdigily.dev/install↗
digily.dev/err-401↗
digily.dev/changelog↗
digily.dev/install
Who reaches for it
Developers, technical writers and small engineering teams
Anyone who has ever had to fix a link in something that had already shipped, and would rather not do it twice.
An error code that resolves to the current troubleshooting page
A download link that picks the right platform build
A docs reference that survives the next site migration
One indirection, forever
Why put a redirect in front of a URL you control?
Because you control it today. The set of URLs you control in five years is smaller than you think, and everything already published assumes otherwise.
https://digily.dev/err-401
- It absorbs migrations: a docs rebuild, a domain change or a platform move becomes one edit instead of a search across every artefact you have shipped.
- It works in read only places: compiled binaries, printed manuals, published packages and other people's blog posts cannot be edited afterwards.
- It stays in one place: links, rules, codes and statistics all live in the same Digily Link account, reachable from the same API key.
Short and direct
digily.dev questions and answers
What it is, how the API works, which redirect status is used and what it costs.
What is digily.dev?
digily.dev is a domain you can choose inside Digily Link when you shorten a URL, build a page or generate a QR code. It is not a separate platform and it does not need its own account.
Is there an API?
Yes. Digily Link exposes an HTTP API covering links, link statistics, projects, tracking pixels, splash pages, QR codes, email signatures, custom domains, teams and account logs. The endpoint list and examples are published at the API documentation page.
How does authentication work?
Every endpoint takes an API key sent as an Authorization bearer header. You generate the key in your account settings and it can be rotated there.
What do the errors look like?
Conventional HTTP status codes, with a JSON body carrying an errors array. 400 for missing or invalid parameters, 401 for a missing or invalid key, 404 for an unknown resource, 429 when the rate limit is exceeded and 500 for a problem on the server side.
What timezone are the timestamps in?
UTC, unless an endpoint says otherwise. That is worth knowing before you compare API output against a dashboard set to local time.
Which redirect status does a link use?
A temporary redirect, which is the correct choice for an editable destination. A permanent redirect would be cached by browsers, so a later change would not reach anybody whose browser had already remembered the old target.
Can one link resolve differently per platform?
Yes. Routing rules can pick the destination by country, device or browser language, which covers platform specific downloads and regional documentation.
Is it free?
Yes, within the limits of the free Digily Link plan, with no card required. Paid plans raise the limits, and API access depends on your plan.
Start on Digily Link
Take a digily.dev address.
Open a free account, get an API key, and put links in your docs that you can still repoint in five years. The address does not change when the infrastructure does.