LEKAB RCS API
lekab.com
- API
What LEKAB RCS API is
LEKAB RCS API helps businesses create branded, interactive conversations inside customers’ messaging apps. It is a REST API using JSON, with OpenAPI/Swagger documentation and webhooks for integration. Messages can contain text, images, carousels, suggested replies, action buttons and rich cards. Businesses can present a sender name, logo and colours verified by Google, while automatic SMS fallback covers recipients whose device or carrier does not support RCS. The API reports delivery status, read receipts and customer responses, and tracks engagement and conversion metrics. LEKAB says messages use verified business profiles and encrypted channels, with service availability designed for 99.99% uptime and SLA support. It is intended to connect with existing customer support and CRM systems. Android support is described as widespread, while iOS availability is expanding. Marketing, logistics and customer service teams are identified users. Sandbox testing follows agent registration and verification; production access can depend on compliance and carrier approvals.
Who it suits
It suits marketing, logistics and customer service teams building two-way business messaging. Developers needing REST, JSON, webhooks and CRM integration can use its API.
Good to know, and what to watch
- Rich message formats include carousels and action buttons
- Automatic SMS fallback reaches unsupported recipients
- Delivery, read and conversion metrics are provided
- Google-verified sender branding is supported
- OpenAPI documentation and webhooks aid integration
- Pricing varies by country and operator
- Production access may require carrier approvals
- iOS support is still expanding
- Requires brand and agent registration
Plans
Every plan and priceLEKAB RCS API
Pricing on request
The verdict
LEKAB RCS API combines branded rich messaging, two-way interactions and delivery analytics with SMS fallback. It is a paid, integration-focused service whose availability and costs depend on operators and approvals.
What the maker publishes
- Analytics
- The API provides delivery status, read receipts and customer responses, and tracks engagement and conversion metrics. source
- API
- The API is RESTful, uses JSON, and provides OpenAPI/Swagger documentation and webhooks. source
- Availability
- The page says RCS is widely supported on Android and that iOS support is expanding as carriers and platforms adopt it. source
- Branding
- Businesses can use a sender name, logo and colours verified by Google. source
- Company history
- LEKAB says it has provided business messaging solutions since 1994. source
- Developer support
- LEKAB offers documentation, code samples and support from its expert team. source
- Developer tools
- The RCS API offers REST with JSON, OpenAPI/Swagger documentation, and webhooks. source
- Device support
- The page says RCS is widely supported on Android and iOS support is expanding, with Nordic availability described as coming soon. source
- Fallback
- The API automatically falls back to SMS when a recipient’s device or carrier does not support RCS. source
- Founded
- 1994 source
- Getting started
- After registering and verifying an agent, customers can test in a sandbox immediately; production access typically takes days, depending on compliance and carrier approvals. source
- Headquarters
- Stockholm, Sweden source
- Integration
- LEKAB says the API is designed to integrate with existing customer support and CRM systems. source
- Integrations
- LEKAB says the API is designed to integrate with existing customer support and CRM systems. source
- Message formats
- Supported formats include text, images, carousels, suggested replies, action buttons and rich cards. source
- Pricing
- Pricing varies by country and operator; the page says standard RCS generally costs one SMS rate, rich RCS costs 1.5 times that rate, and conversational messages within 24 hours cost twice that rate. source
- Purpose
- LEKAB RCS API lets businesses build interactive, verified and branded conversations in customers’ messaging apps. source
- Reliability
- LEKAB states the service is built for 99.99% uptime with SLA support. source
- Security
- LEKAB says messages use verified business profiles and encrypted channels. source
- Service reliability
- LEKAB states the RCS service is built for 99.99% uptime with SLA support. source
- Support
- LEKAB offers support from its expert team and directs prospective customers to contact sales to get started. source
- Who it serves
- The page describes use by marketing, logistics and customer service teams. source
Checked against the maker's pages on 8 Oct 2026.