Please Wait...
Learn how to authenticate and start using the SPRL REST APIs.
SPRL provides a secure REST API that allows developers to integrate URL shortening, QR Code generation, messaging services, email verification, analytics, and other platform features directly into their own applications.
Whether you're building a website, mobile app, CRM, ERP, e-commerce platform, or automation workflow, the SPRL APIs make it easy to interact with the platform programmatically over HTTPS.
Depending on your subscription and enabled services, you can integrate:
| API | Description |
|---|---|
| Short Link API | Create, update and manage short URLs programmatically. |
| QR Code API | Generate QR Codes for links and campaigns. |
| SMS API | Send transactional and promotional SMS messages. |
| Email API | Send email campaigns and transactional emails. |
| Email Verification API | Validate email addresses before sending campaigns. |
| WhatsApp API | Integrate WhatsApp Business messaging (where available). |
Before making your first API request, complete the following steps.
| Step | Action |
|---|---|
| 1 | Create or sign in to your SPRL account. |
| 2 | Navigate to Dashboard → API & Services → HTTP REST API Keys. |
| 3 | Generate a Live API Key or Test API Key. |
| 4 | Save your Client ID and Client Key securely. |
| 5 | Use the credentials to authenticate your API requests. |
| Live API Keys | Test API Keys |
|---|---|
| Used in production applications. | Used only for development and testing. |
| Can perform live operations. | Uses sandbox endpoints. |
| Consumes actual account resources where applicable. | Does not perform live operations. |
| Suitable for production deployments. | Recommended during application development. |
All protected API requests require authentication using yourClient ID and Client Key. These credentials identify your application and authorise access to your account.
All requests must be sent over HTTPS.
The API Key Manager allows you to create and manage separate credentials for different applications or websites. When generating a key, you'll be asked to provide the request domain for organisational purposes.
Each generated key includes:
For security reasons, the Client Key is displayed only once when it is generated. Store it securely before leaving the page.
SPRL follows modern API security practices to help protect customer applications and data.
| Problem | Possible Solution |
|---|---|
| Authentication failed | Verify your Client ID and Client Key. |
| Permission denied | Ensure the API feature is enabled for your account. |
| Rate limit exceeded | Reduce request frequency and retry later. |
| Invalid request | Verify the endpoint, request headers and payload. |
Yes. Most API endpoints require authentication using your Client ID and Client Key.
Yes. You can generate multiple API keys for different applications or environments.
Yes. Test Keys are recommended during development before moving to Live Keys for production.
Yes. Unused or compromised API keys should be removed immediately.
Our support team is always happy to assist you.
We use cookies to improve your experience, analyse traffic, and personalise content. By clicking “Accept”, you consent to the use of cookies as described in our Cookie Policy .
Accept cookies Read our Cookie Policy
