Skip to main content

Getting Started with Qlara Partner Gateway

Welcome to the Qlara Partner Gateway—your unified platform for multi-channel messaging. Send SMS, RCS, and WhatsApp messages through a single REST API, manage contacts and campaigns, and track delivery in real time.

What You Can Do​

The Qlara Partner Gateway enables:

  • Multi-channel messaging: Reach customers via SMS, RCS, or WhatsApp from one API endpoint
  • Campaign management: Create, schedule, and monitor large-scale campaigns
  • Contact management: Store and organize customer lists
  • Real-time delivery tracking: Monitor message status instantly via webhooks or polling
  • Two-way conversations: Receive replies and build interactive workflows
  • Templates: Pre-approve messaging templates for compliance and speed

Base URL​

All API requests go to:

https://lora-api.agiletelecom.com/api

Authentication​

Two authentication methods are available. API Key is recommended for most use cases.

API Key (Recommended)

  • Include the API key in the X-Api-Key header
  • No expiration; regenerate if compromised
  • See Authentication Guide for examples

Basic Authentication

  • Encode credentials in base64
  • Alternative if API keys aren't suitable
  • See Authentication Guide for setup

Both methods support optional IP Whitelisting as an additional security layer.

Messaging Channels​

SMS​

Universal reach, no template approval required. Every mobile phone receives SMS.

RCS (Rich Communication Services)​

Rich media delivery on Android devices. Requires template approval. Falls back to SMS on unsupported devices.

WhatsApp​

Meta-approved templates and 24-hour messaging window. Premium reach with advanced features.

System Fallback Chain Messages attempt delivery in this order: WhatsApp → RCS → SMS. If WhatsApp delivery fails, the system automatically tries RCS, then SMS.

See Messaging Channels for feature comparison and selection guidance.

Essential Concepts​

Channels
SMS, RCS, and WhatsApp are the available channels. Each has different capabilities and approval requirements.

Contacts & Lists
Store customer phone numbers and attributes. Organize into lists for bulk campaigns.

Campaigns
Send messages to multiple contacts on a schedule. Track costs and delivery analytics throughout the campaign lifecycle.

Webhooks
Real-time notifications when message status changes. Webhooks post delivery events to your server as they occur.

Templates
Pre-formatted message content approved by carriers or platforms. Required for RCS; optional but recommended for SMS and WhatsApp.

Next Steps​

  1. Quick Start — Send your first message in 3 minutes
  2. Authentication — Securely authenticate API requests
  3. Messaging Channels — Understand capabilities and reach
  4. Webhooks — Set up real-time delivery tracking
  5. Campaigns — Manage large-scale messaging

Ready to send your first message? Jump to Quick Start.