Create your first link
Publish a short link, change its destination, and confirm that analytics work.
This guide assumes that Masir is running and the first owner account exists.
Create the link
- Open
/loginand sign in. - Select New link.
- Enter a destination such as
https://example.com/docs. - Enter
docsas the slug, or leave it empty to generate one. - Select Create link.
Masir shows the full short URL. The public address uses NUXT_PUBLIC_SHORT_DOMAIN and the workspace link prefix, when one is set.
Verify the redirect
Open the short URL in a new browser tab, or inspect it from a terminal:
curl -I https://go.example.com/docsThe response is 302 and the Location header contains the destination.
Change the destination
Open the link, replace its destination, and save. Open the same short URL again. It now sends the visitor to the new destination.
The public link did not change. This is the main reason to put Masir between a shared address and its current destination.
Check the traffic
Open the link analytics panel. It shows requests by time, outcome, referrer, country, device, browser, and bot class.
Masir uses a daily salted hash to count unique visitors. It does not store the source IP address or user-agent string.
Check the change history
Open the history panel for the link. It shows the recent changes, the user who made each change, and the fields that changed.
Workspace owners can also open the workspace activity log for link, campaign, member, and security events.
Optional: use the HTTP API
Sign in and save the session cookie:
curl -sS -X POST https://go.example.com/api/auth/login \
-H 'content-type: application/json' \
-d '{"email":"you@example.com","password":"your-password"}' \
-c cookie.txtCreate another link:
curl -sS -X POST https://go.example.com/api/links \
-H 'content-type: application/json' \
-b cookie.txt \
-d '{"destinationUrl":"https://example.com","slug":"example"}'Masir does not have API tokens yet. The API uses the same session cookie as the interface.