Wennov Connect
SMS API for developers
Integrate SMS sending into your application with one REST call, and receive real delivery state by webhook.
One call to send. One webhook to know what happened.
No mandatory SDK, and no documentation that drifts behind the code.
The Wennov Connect API is plain REST with key authentication. The OpenAPI documentation is generated from the platform real routes, so it never falls out of sync with the implementation.
Read the docsWhat the API gives you
- Single or batch sending across SMS, email, WhatsApp or voice, with the same request shape
- Query a message state: dispatch state kept separate from real delivery state confirmed by DLR
- Batch status lookup for hundreds of messages at once, instead of one call per message
- Signed webhooks for message delivered, message failed, reply received and unsubscribe
- A delivery log for every webhook, with manual retry from the interface
- Idempotent requests: a network retry never sends the message twice
- Scoped API keys with configurable expiry and rotation with a grace period
- IP restriction and per-key rate limits
- A separate test environment, with messages clearly labelled as sandbox
About delivery state
A common integration mistake is treating the send response as delivery confirmation. It is not. A success response means the message was accepted and queued. The real outcome arrives later, when the carrier returns the DLR. Our API separates the two explicitly: one field for dispatch state, one for confirmed delivery state, plus a flag telling you whether the result is final. We recommend webhooks over repeated polling.
Frequently asked questions
Is there an official SDK?
The API is standard REST with header authentication, so it works with any HTTP library in any language. We publish an OpenAPI specification you can generate a client from if you prefer.
How do I know a message actually arrived?
Subscribe to the message.delivered and message.failed webhook events, or query the message status endpoint. Do not rely on the send response: that only confirms acceptance into the queue.
What if my server is down when you send a webhook?
We retry automatically, and every delivery has its own log visible in the interface. You can manually retry any failed delivery, so you do not lose events to a temporary outage.
Can I test without sending real messages?
Yes, there is a test environment. Messages sent in sandbox are clearly labelled in reports so they are never confused with real traffic.
How do I protect API keys?
Every key is scoped, so a send-only key cannot read your contact database. You can set an expiry, restrict by IP address, and rotate the key with a grace period during which both versions work.
Get an API key and send your first message
The free account includes API access and the test environment.
Create accountContact
Tell us your use case and we will recommend the best setup.
Email: office@wennov.ro
Phone: +40 731 177 744
Location: București, România