LEKAB RCS API
LEKAB RCS API lets businesses create branded, interactive conversations in customers’ messaging apps.
What LEKAB RCS API is
LEKAB RCS API lets businesses create branded, interactive conversations in customers’ messaging apps. The REST API uses JSON and includes OpenAPI/Swagger documentation and webhooks. Supported message formats include text, images, carousels, suggested replies, action buttons and rich cards. Businesses can send from a name, logo and colours verified by Google; when a device or carrier does not support RCS, the API falls back to SMS. Delivery status, read receipts and customer responses are available, along with engagement and conversion metrics. LEKAB says the messages use verified business profiles and encrypted channels, and that the service is built for 99.99% uptime with SLA support. The API is designed to connect with existing customer support and CRM systems. Pricing varies by country and operator: standard RCS generally costs one SMS rate, rich RCS 1.5 times that rate, and conversational messages within 24 hours twice that rate. RCS is described as widely supported on Android, with iOS support expanding. LEKAB offers documentation, code samples and expert support; production access typically takes days, depending on compliance and carrier approvals.
Good
- Supports rich media and action buttons
- Verified sender branding with name, logo and colours
- SMS fallback for unsupported devices or carriers
- Reports delivery, reads and customer responses
- Includes webhooks and OpenAPI/Swagger documentation
Watch out
- Pricing varies by country and operator
- iOS support is still expanding
- Production access can depend on approvals
- Requires brand and agent registration
Who it suits
The API is aimed at marketing, logistics and customer service teams that want branded, two-way messaging. It may suit developers integrating messaging with customer support or CRM systems.
Verdict
LEKAB RCS API combines branded RCS messages with response and engagement reporting, plus SMS fallback. Check operator pricing and device support in your target markets before planning an integration.
Plans and prices
From LEKAB RCS API's own pricing page, checked 8 Oct 2026.
| Plan | Price | What it gives you |
|---|---|---|
| LEKAB RCS API | Priced on request | Requires brand and agent registration; production access depends on compliance and carrier approvals · Pricing varies by country and operator; the page says a standard RCS message costs the same as one SMS, a rich RCS message costs 1.5 times the standard rate, and conversational messages within a 24-hour window cost twice the standard rate. |
The facts
Each one read from LEKAB RCS API's own pages, with the date it was checked.
What it does
- Analytics
- The API provides delivery status, read receipts and customer responses, and tracks engagement and conversion metrics.checked 8 Oct 2026
- API
- The API is RESTful, uses JSON, and provides OpenAPI/Swagger documentation and webhooks.checked 8 Oct 2026
- Availability
- The page says RCS is widely supported on Android and that iOS support is expanding as carriers and platforms adopt it.checked 8 Oct 2026
- Branding
- Businesses can use a sender name, logo and colours verified by Google.checked 8 Oct 2026
- Developer support
- LEKAB offers documentation, code samples and support from its expert team.checked 8 Oct 2026
- Developer tools
- The RCS API offers REST with JSON, OpenAPI/Swagger documentation, and webhooks.checked 8 Oct 2026
- Fallback
- The API automatically falls back to SMS when a recipient’s device or carrier does not support RCS.checked 8 Oct 2026
- 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.checked 8 Oct 2026
- Integration
- LEKAB says the API is designed to integrate with existing customer support and CRM systems.checked 8 Oct 2026
- Integrations
- LEKAB says the API is designed to integrate with existing customer support and CRM systems.checked 8 Oct 2026
- Message formats
- Supported formats include text, images, carousels, suggested replies, action buttons and rich cards.checked 8 Oct 2026
- 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.checked 8 Oct 2026
- Purpose
- LEKAB RCS API lets businesses build interactive, verified and branded conversations in customers’ messaging apps.checked 8 Oct 2026
- Reliability
- LEKAB states the service is built for 99.99% uptime with SLA support.checked 8 Oct 2026
- Security
- LEKAB says messages use verified business profiles and encrypted channels.checked 8 Oct 2026
- Service reliability
- LEKAB states the RCS service is built for 99.99% uptime with SLA support.checked 8 Oct 2026
- Support
- LEKAB offers support from its expert team and directs prospective customers to contact sales to get started.checked 8 Oct 2026
- Who it serves
- The page describes use by marketing, logistics and customer service teams.checked 8 Oct 2026
The company
- Company history
- LEKAB says it has provided business messaging solutions since 1994.checked 8 Oct 2026
- Founded
- 1994checked 28 Sep 2026
- Headquarters
- Stockholm, Swedenchecked 28 Sep 2026
Where it runs
- Device support
- The page says RCS is widely supported on Android and iOS support is expanding, with Nordic availability described as coming soon.checked 8 Oct 2026
Alternatives to LEKAB RCS API
- 1
nativeMsg RCS Business Messaging
Free planAndroidiOSWebAPI8.0From $199 a month - 2
SimplyRCS
Free planOpen sourceWebAPISelf-hosted7.8From $20 a month - 3
RCS-Box
Free planWebAPI7.3From €49 a month - 4
SMS.es Business Messenger
Free planWebAPI7.3From €39 a month - 5
Gupshup
Free planWebAPI7.2Free plan - 6
Orbit by Devotel
Free planWebAPISelf-hosted6.8Free plan