Managed destination
Keep the public keyname stable while controlling its active and blocked destinations from the panel.
API service
SmartURLs combines a managed destination with Stopbot visitor detection, allowing each visit to receive a redirect decision and its supporting traffic context.
GET /services/shorterlinkHow it works
A SmartURLs request uses a registered keyname together with visitor IP and optional user-agent context. Stopbot evaluates the visit, records its result, and returns the redirect destination for the active link configuration.
uniqueCode is returned only when JavaScript verification is enabled and a verification token is issued. The client uses that token for the follow-up verification request.GET /services/shorterlinkredirectToDestination selected by the active SmartURLs configurationblockAccessAccess decision produced for the current visitjsResponseShows whether JavaScript verification is enabled for the linkuniqueCodeOptional token used by the JavaScript verification flowIntegration examples
Send the registered keyname and visitor context, then use the returned JSON to continue the configured redirect and verification flow.
Replace the keyname placeholder with one owned by the API account and handle redirectTo, jsResponse, and uniqueCode according to the documented flow. Read the complete SmartURLs documentation.
Core capabilities
Keep the public keyname stable while controlling its active and blocked destinations from the panel.
Uses traffic context and configured country, device, and detection rules when deciding where a visit goes.
Supports an optional second step that records whether the visitor executed the browser verification flow.
Records SmartURLs visitor results so link activity can be reviewed from the Stopbot panel.
Use cases
Use one managed link while retaining control over destination and visitor filtering rules.
Send visits to destinations that fit the configured device and geographic policy.
Review redirect activity together with detection decisions and visitor network context.
Create an account, configure the service in the Stopbot panel, and follow the integration documentation for your application.