Everything you need to know about secure links.
Learn how SURLs.me works, how secure URLs can be protected, how access controls work, and how you can integrate programmable links into your applications and workflows.
General
01 / General01 What is SURLs.me?
SURLs.me is a secure programmable URL platform for creating and managing short links with configurable access controls.
Depending on the configuration, a link can use password protection, PIN protection, OTP-based protection, expiration, usage limits, IP and country restrictions, geographic controls, device-related controls, allowed referrers, and analytics.
02 How is SURLs.me different from a regular URL shortener?
A traditional URL shortener primarily converts a long URL into a shorter address.
SURLs.me adds programmable access policies around short URLs. This allows a link owner to define conditions such as authentication, expiration, usage limits, geographic restrictions, IP restrictions, device-related controls, and allowed referrers.
03 What can I use SURLs.me for?
SURLs.me can be used for secure document sharing, temporary resources, event invitations, marketing campaigns, internal resources, controlled downloads, application workflows, and other situations where a short URL needs configurable access rules.
04 Can I create a custom short URL?
Yes. SURLs.me supports custom short paths for supported links. Custom paths can be useful for branded campaigns, events, product launches, internal resources, and memorable links.
Security & protection
02 / Protection05 Can I password protect a short URL?
Yes. SURLs.me supports password-protected URLs. A visitor must satisfy the configured password requirement before accessing the protected destination.
06 Can I protect a URL with a PIN?
Yes. PIN protection can require a visitor to provide a configured numeric access code before the destination can be accessed.
PIN protection is useful when the link and its access code are intended to be shared separately.
07 Does SURLs.me support OTP-protected links?
SURLs.me supports OTP-oriented URL protection for supported link configurations.
OTP delivery, expiration, retry behavior, and verification details should follow the current SURLs.me product and API documentation.
08 Can I make a link expire automatically?
Yes. SURLs.me supports expiration controls for supported links.
An expiration policy can make a link available only until a configured time or expiration condition.
09 Can I limit how many times a URL can be used?
Yes. SURLs.me supports usage limits for supported links. A link can be configured so access is limited to a defined number of uses.
The exact definition of a usage event depends on the applicable SURLs.me implementation.
Access controls
03 / Access10 Can I restrict a link by IP address?
Yes. SURLs.me supports IP-based access controls for supported link configurations.
IP restrictions can be used to control access based on the network IP associated with an incoming request.
11 Can I restrict a URL to specific countries?
Yes. SURLs.me supports country-based access controls for supported links.
Country restrictions can be useful when a destination should only be accessible from selected geographic regions.
Country information derived from IP geolocation should be treated as an estimate rather than precise physical location.
12 Does SURLs.me support geofencing?
SURLs.me supports geographic access-control functionality for supported configurations.
Geographic restrictions can be used when access needs to depend on configured geographic conditions.
IP-derived geographic information should not automatically be interpreted as precise GPS-level device location.
13 Can I restrict a link based on the device being used?
SURLs.me provides device-related access-control capabilities for supported configurations.
The exact device-identification method and supported device attributes depend on the current SURLs.me implementation.
14 What are allowed referrers?
Allowed referrers are an access-control mechanism that can restrict a link based on referring information associated with an incoming request.
Referrer information is controlled by the browser and client environment and may be absent or modified. It should therefore not be treated as equivalent to cryptographic authentication.
Link management
04 / Management15 Can I use SURLs.me for temporary links?
Yes. Expiration controls make SURLs.me suitable for temporary links such as event resources, invitations, temporary documents, campaigns, and other time-limited destinations.
16 Can I use SURLs.me for private document sharing?
SURLs.me can be used to create controlled links to documents and other resources.
Depending on the required protection level, supported links can use passwords, PINs, OTP verification, expiration, usage limits, geographic restrictions, or other available access controls.
17 Can I use SURLs.me for marketing campaigns?
Yes. SURLs.me can be used for campaigns that benefit from short URLs, custom paths, access controls, expiration, usage restrictions, and link analytics.
18 Can I use SURLs.me for event links and invitations?
Yes. SURLs.me can be useful for event invitations, registrations, temporary event resources, and controlled-access links.
Expiration, authentication, usage limits, and other supported controls can be configured according to the requirements of the link.
Analytics & API
05 / Platform19 Can SURLs.me provide analytics for my links?
SURLs.me provides link usage and access analytics for supported links.
Depending on the available configuration, analytics can include information such as access time, usage counts, IP-related information, geographic information, device information, and referrer information.
20 Does SURLs.me provide an API?
Yes. SURLs.me provides API-oriented integration capabilities for supported platform operations.
Developers should use the official API documentation for current authentication requirements, endpoints, request formats, response formats, errors, permissions, and supported operations.
21 Can I create SURLs.me links programmatically?
Yes. Applications can integrate with SURLs.me through its API capabilities where supported.
API-specific behavior should always be implemented according to the current official API documentation rather than inferred from the marketing website.
22 Where can I find the SURLs.me API documentation?
The official SURLs.me API documentation is available at surls.me/api-documentation .
Security & privacy
06 / Security23 Is a short URL itself considered secure?
A short URL should not be treated as a secret simply because it is difficult to guess.
For sensitive resources, use an appropriate authentication or access-control mechanism and follow the security requirements of the application protecting the destination.
24 Does SURLs.me reveal a visitor's exact physical location?
IP-based geographic information is generally an approximation and should not be represented as a visitor's exact physical location.
Geographic accuracy depends on the network and geolocation information available to the platform.
25 What information can SURLs.me use for access controls?
Depending on the link configuration, access policies can involve authentication requirements, expiration, usage limits, IP information, country information, geographic conditions, device-related information, and referrer information.
26 Should I put API keys or passwords inside a SURLs.me URL?
No. API keys, passwords, access tokens, and other secrets should not be placed directly in URLs.
Keep credentials server-side and use the documented authentication and access-control mechanisms provided by your application and SURLs.me.
27 Where can I get help with SURLs.me?
For product questions, technical questions, API issues, enterprise requirements, or other enquiries, visit the SURLs.me contact page .
Need help with a secure link?
If you cannot find what you are looking for, contact the SURLs.me team or explore the API documentation for integration-specific details.