Put shortening between destination creation and delivery
Build the complete destination first, including the path and query parameters your application needs. Send that URL to URLMe from your server, then insert the returned short URL into the final message handed to your SMS provider.
- Create the destination in your application
- Call POST /v1/links from a trusted server
- Insert shortUrl into the SMS template
- Send through your existing provider
Keep the API key out of message clients
The URLMe key belongs in a server-side secret manager or protected environment variable. Never call the shortening endpoint from browser JavaScript, a mobile app, or a template that could expose the Bearer token.
curl --request POST "https://api.urlme.link/v1/links" \
--header "Authorization: Bearer $URLME_API_KEY" \
--header "Content-Type: application/json" \
--data '{"url":"https://example.com/orders/8421/status?source=sms"}'Choose the link scope deliberately
Create one shared link when every recipient should reach the same public destination. Create recipient-specific links only when the destination genuinely differs and your own application is authorized to encode that recipient context.
Use a recognizable hostname when trust matters
Starter can return urlme.link URLs immediately. Growth and Scale can use a verified custom hostname, which keeps the visible domain aligned with the sender customers already recognize.