Brief
What we set out to achieve
- Reliable SMS delivery for bookings
- A simple connection to any booking system
- An overview of the delivery and the cost of every message
Challenge
Why we took it on
Our clients' booking systems needed to send text messages: a confirmation right after booking, a reminder before the appointment and a notice on cancellation. Calling people by hand takes up staff time.
The solution had to be reliable, easy to connect to different systems, and it had to show whether the message really arrived. When a carrier rejects an SMS, you need to know before the client fails to show up.
Solution
What we did and why
A simple REST API. A REST API is an agreed way for two systems to send data to each other. The booking system sends one request with a number and a text, and the API takes care of sending it through the SMS gateway. The API comes with documentation and command line tools (CLI) for testing and maintenance.
Three types of messages. A booking confirmation, a reminder before the appointment and a cancellation notice.
Delivery overview. For every SMS you can see the client, the recipient, the text, the number of parts, the delivery status, the price and the time it was sent. Messages can be filtered by client, status, number or date, and the summary shows today, the current month, delivered and failed messages and the costs.
For several clients. One API serves several businesses at once. Each has its own sender name (for example “OptikPetrik”) and its own statistics.
Live in production. The booking system uses the API Optik Petrík: a confirmation goes out after booking and a reminder the day before the appointment.
Delivery
What the project includes
- A REST API with documentation
- Command line tools (CLI) for testing and maintenance
- Automated confirmations, reminders and cancellation notices
- An overview with delivery status, filters and costs
- A record of the reason when a carrier rejects a message
- Live deployment for Optik Petrík
Results
What you can verify
The number of delivered messages comes from the delivery overview of 7/16/2026 (screenshot below), that is from the first days of live operation.
Process
How the project ran (2 weeks)
-
Design
The API specification and the choice of SMS gateway.
-
Development
A REST API, a database, a message queue and CLI tools.
-
Testing
Deliverability and behavior when the carrier returns an error.
-
Integration
Connection to the client's booking system.
Technologies
What it runs on
- REST API
- an interface that lets another system send an SMS with a single request
- PHP and an SQL database
- sending, logging and statistics for messages
- CLI
- command line tools for tests and maintenance
- SMS gateway
- a service that delivers the message to the mobile network and returns the delivery status
Gallery
Examples
(opens the full size image in a new window)
(opens the full size image in a new window)