Bulk Shortening with Nested Route | DLT-Compliant SMS API for Bulk Short URLs

Bulk Shortening with Nested Route (DLT-Compliant SMS)

Base URL: https://insprl.com/api

POST /url/bulk-url-shortener-nested-route

If you send SMS campaigns at scale in India, ensuring compliance with DLT (Distributed Ledger Technology) is crucial. The Bulk Shortening with Nested Route API by SPRL helps you create multiple short URLs in one request, while aligning with TRAI’s DLT framework.

This API is ideal for bulk SMS dispatch where every message may include a shortened URL, such as OTP links, tracking URLs, campaign CTAs, or custom user journeys, all fully compliant with DLT-registered templates, sender headers, and routes.

Request Information

Method	POST
Request URL	https://insprl.com/api/url/bulk-url-shortener-nested-route
Authentication	Required How to Generate API keys?

Header Parameters

Header	Yes	Description
Authorization	Yes	Bearer {CLIENT_KEY}
Content-Type	JSON	Supported values: `application/x-www-form-urlencoded` `application/json`

Request Parameters

Parameter	Type	Validate	Description
client_id	String	Required	Use your "CLIENT ID" for this Parameter
urls	Array	Required	Add multiple urls (Up to 1000) which you want to get shorter.
nested_path	String	Required, Max 50 chars, Pattern: ^[a-zA-Z0-9\-_]+$	Nested route to append to the short URL. Only letters, numbers, hyphens, and underscores are allowed.
slug_prefix	String	Optional	Allowed only alpha-numeric characters, underscores, and dashes.
domain	String	Optional	Specify if you want to use custom domain
expiry_date	Date	Optional	Date format: dd-mm-yyyy
response_mode	String	Optional	"plain" (Default) or "along" (Pass the reference key to receive in response)

Response Parameters

Parameter	Type	Description
code	Numeric	Find the code information below under "API Codes"
message	String / Array	As per the request handler
short_urls	Array	List of Shorten URLs

Request Example

Select Language

Response Structure Examples

Select Response Type

Response Codes

SPRL Code	HTTP Status	Mode	Response Field	Description
100	200	success	data	Request processed successfully.
101	401	failed	message	Authentication failed. Invalid or missing API credentials.
102	422	failed	errors	Parameter validation failed. Check the input fields.
103	403	failed	error	SPRL account is restricted (temporary or permanent block).
104	400	failed	errors	Insufficient wallet balance. Recharge required.
105	500	failed	message	Unexpected server error. Please try again later.
129	429	failed	errors	API usage limit exceeded (daily, monthly, or total).

Error Flag Reference

Category	Flag	Type	Description
Account	`ACCOUNT_PERMANENT_BLOCKED`	account_restricted	The SPRL account has been permanently blocked.
Account	`ACCOUNT_TEMP_BLOCKED`	account_restricted	The SPRL account has been temporarily restricted.
Billing	`INSUFFICIENT_BALANCE`	billing_error	The wallet balance is insufficient to process the request.
Rate Limit	`DAILY_LIMIT_REACHED`	rate_limit_exceeded	The daily API usage limit has been exceeded.
Rate Limit	`MONTHLY_LIMIT_REACHED`	rate_limit_exceeded	The monthly API usage limit has been exceeded.
Rate Limit	`TOTAL_LIMIT_REACHED`	rate_limit_exceeded	The total API usage limit has been exceeded.
Validation	`INVALID_PARAMETER`	validation_error	One or more request parameters are invalid.
Authentication	`INVALID_CREDENTIALS`	auth_error	API credentials are missing or invalid.
Server	`UNEXPECTED_ERROR`	server_error	An unexpected internal server error occurred.