SMS / Messaging REST Service with SOAP Gateway Bridge
Overview
An SMS/messaging backend built on the Symfony REST Edition, exposing a HATEOAS REST API while bridging to a legacy SOAP messaging gateway via NuSOAP. Part of the author’s cluster of telephony/communications builds alongside callinfo and sip.
The Challenge
SMS aggregators and carrier services of the era commonly exposed SOAP endpoints, while modern apps wanted clean REST. The project sits in the middle: a JSON/HATEOAS REST API on the front, talking SOAP to the messaging gateway behind.
What We Built
A Symfony 2.3 REST Edition application with FOSRestBundle, JMS Serializer, BazingaHateoas and NelmioApiDoc for a documented, hypermedia REST API; NuSOAP registered as a Composer package to call the SOAP messaging gateway; JWT authentication and FOSUserBundle/FOSMessageBundle for accounts and messaging; Pusher for real-time delivery; FOSHttpCache for HTTP caching; and Goutte plus ddeboer/data-import for scraping/importing data. Custom bundles live under src/.
Technologies & Approach
The Symfony REST Edition gave a batteries-included REST stack (HATEOAS, templated URIs, API docs); NuSOAP handled the awkward SOAP interop; JWT and Pusher covered stateless auth and live updates. A pragmatic mix bridging old and new integration styles.
Outcome / Impact
Demonstrated building a modern REST/HATEOAS API that interoperates with a legacy SOAP messaging system, a real-world integration challenge, within the communications/telephony problem space.
Capabilities Demonstrated
- Bridging REST APIs to legacy SOAP gateways (NuSOAP)
- Designing HATEOAS / hypermedia REST APIs with FOSRest
- Stateless JWT auth and real-time delivery via Pusher
- Data import/scraping pipelines with Goutte and ddeboer/data-import