Service notice regarding the iSMS Scheduler API.
We regret to inform that the iSMS SMS Scheduler API (isms_scheduler.php) has been permanently discontinued and is no longer available.
The endpoint was retired to protect platform stability and delivery quality for all users. Scheduling is still fully supported — through the portal, or from your own system via the standard SMS API.
We apologise for any inconvenience this may cause to legitimate users. Please see the alternatives below — the web portal scheduler and standard SMS API both provide reliable scheduling capabilities without the API endpoint.
The iSMS web portal includes a built-in SMS scheduler. When composing SMS, select "Send Later" and set your desired date and time. Supports one-time and daily schedules.
Scheduler guide →For developers, implement scheduling on your own server using a cron job that calls the standard iSMS HTTP/HTTPS SMS API at your desired time. This gives you full control over scheduling logic.
SMS API Documentation →Use our REST API to trigger SMS sends programmatically from your own application logic — including your own scheduling system, workflow automation, or CRM integration.
REST API Reference →If you require scheduled messaging at scale with custom logic, contact our team. We can advise on the best integration approach for your use case.
Contact Our Team →If your system still calls isms_scheduler.php, those requests are no longer answered and should be removed. Replace them with either of the following:
Option 1 — schedule in the portal. Compose the message, choose Send Later, set the date and time. Nothing to build. Scheduler guide →
Option 2 — schedule on your side. Keep your own cron or job scheduler, and call the standard SMS API at the moment you want the message to go out. You keep full control of the timing logic, retries and cancellation. SMS API documentation →
Credentials, sender IDs, IP whitelisting and billing are unchanged — only the scheduling call goes away.