Scheduled go-live
After this page, you can share a link before launch day, choose where early taps go, and have it switch to its real destination by itself at the time you set.
On this page 7
- Time
- About 5 minutes
- You need
- A link, in the dashboard or created with a secret key. For "Send to the app store", your app's store details in Settings.
- Works on
- Dashboard, or any server through the REST API
Print the poster, schedule the WhatsApp broadcast and send the email before the sale starts. Until the go-live time, the link isn't live yet, and you choose where taps go. From that moment it opens its destination like any other link.
1. Set the go-live time
In Dashboard → Links, open the link's edit panel and fill in Goes live. The time is in your own time zone, which the label shows. Leave it blank for a link that is live now.
You should see: a Goes live … chip in the link's edit panel, with the date, time and time zone.
2. Choose where taps go before then
Once a go-live time is set, the panel asks Before it goes live, send people to:
| Option | What people see |
|---|---|
| Show a 'coming soon' page (default) | A short page saying the link isn't live yet and when it opens, with your app's name and a link to your website. |
| Send to the app store | Google Play on Android, the App Store on iPhone, from your app configuration, so people can install ahead of launch. Computers, and phones whose store isn't set up, go to the web page you give here, else the coming-soon page. |
| Send to a web page | Everyone goes to the https page you choose until the link goes live. |
Save the link.
You should see: your choice saved on the link. In the dashboard Playground, each device shows Not live yet: gets the link's before-launch destination.
3. Or do it with the API
POST /v1/links, POST /v1/links/batch and PATCH /v1/links/{slug} accept:
startsAt: epoch milliseconds or an ISO 8601 date-time. It must be beforeexpiresAtif the link has one. In a PATCH,nullmakes the link live now.notLiveAction:page,storeorurl. Leave it out for the coming-soon page.notLiveUrl: an https page. Required withurl; withstore, it's where computers go. It passes the same phishing and malware check as every destination.
curl -X POST https://strait.link/v1/links \
-H "Authorization: Bearer $SECRET_KEY" \
-H "Content-Type: application/json" \
-d '{
"slug": "diwali-sale",
"longUrl": "https://shop.example.com/sale/diwali",
"startsAt": "2026-10-20T00:00:00+05:30",
"notLiveAction": "store"
}'You should see: 201 with the link, including startsAt as epoch milliseconds and notLiveAction: "store".
4. Check it before and after
Ask GET /v1/simulate what a tap would do. It records nothing:
curl "https://strait.link/v1/simulate?url=https://hilltop.strait.link/diwali-sale&ua=android" \
-H "Authorization: Bearer $SECRET_KEY"You should see: "decision": "not_live" and "notLiveTo": "store" before the go-live time, and the link's normal decision after it.
What counts before go-live
Taps before the go-live time are not counted: they aren't recorded in Analytics, never count toward your plan's taps, and send no link.clicked webhook. Link previews still work, so a link shared ahead of launch unfurls in WhatsApp and other chat apps with its title and image. After the go-live time, every tap is recorded and billed as usual.
Common errors
400"startsAt must be before expiresAt". The link would expire before it goes live. Move one of the two times.400"notLiveAction "url" needs notLiveUrl (an https URL)". SendnotLiveUrlwithurl, or pickpage.400"notLiveUrl needs notLiveAction "url" or "store"". The coming-soon page has no web page; dropnotLiveUrlor change the action.
Next steps
- Country rules: send people in some countries to a different web page.
- Short links: the other end of a link's life, where taps go after it expires.