RASL
RASL | DashboardContact
RASL | DashboardContact
Instagram
    RASL
    • Introduction
    • Changelog
    • Messages
      • Overview
      • Message Bot Management
        • List Message Bots
        • Get Message Bots Details
      • Send Simple Message
        POST
      • Send Media Message
        POST
    • Templates
      • Overview
      • Template Management
        • Template Bot
          • List Template Bots
          • Get Template Bots Details
        • List Templates
        • Get Template Details
      • Send Authentication Template
        POST
      • Send Template Message
        POST
    • Contacts
      • Overview
      • Create a New Contact
        POST
      • List Contacts
        GET
      • Get Contact Details
        GET
      • Update Contact Information
        PUT
      • Delete Contact
        DELETE
    • Groups
      • Overview
    • Statuses
      • Overview
    • Sources
      • Overview
    • Integrations
      • N8N Webhook Integration
      • Webhook Format Reference
      • eCommerce Webhook Integration
        • Webhook Listener
        • WooCommerce Webhook Setup
    RASL | DashboardContact
    RASL | DashboardContact
    Instagram

    Welcome to the RASL

    WhatsApp API Documentation
    RASL API enables seamless integration with WhatsApp messaging,
    allowing you to manage messages, templates, contacts, groups,
    statuses, and data sources from your membership in www.getrasl.io
    The API is designed to support a wide range of WhatsApp use cases,
    including bot-driven conversations, template messaging, and customer
    data management — all from a single, unified platform.
    RASL API is production-ready and actively maintained to support
    reliable, real-world integrations at scale.

    WhatsApp Messaging Model#

    RASL follows Meta’s official WhatsApp messaging rules to ensure
    compliant and reliable message delivery.
    Simple (text, media) messages: are subject to Meta’s 24-hour messaging window policy.
    Media messages: support images, documents, audio, and video files.
    Template messages: can be sent outside the 24-hour window using approved WhatsApp templates.
    Understanding this messaging model is essential when choosing between
    session-based messages and template-based messages.

    How the API is Organized#

    The RASL API is organized into clear functional sections to help
    developers quickly understand the platform and locate the appropriate
    endpoints.

    Authentication#

    RASL API uses Bearer Token Authentication.
    All API requests must include a valid API token in the
    Authorization header:
    Authorization: Bearer YOUR_API_TOKEN
    Requests without a valid token will be rejected.

    API Resources Summary#

    RASL API provides the following core resources:
    Messages – Send WhatsApp messages (text, media)
    Templates – Send and manage WhatsApp template messages, including authentication (OTP) delivery.
    Contacts – Manage customer contacts and information
    Groups – Organize contacts into groups
    Statuses – Manage contact statuses
    Sources – Track contact sources and origins
    Integrations – Integrate with CRM, ERP, applications and websites via webhooks, with built-in support for N8N and other automation platforms.
    Connect RASL with eCommerce platforms (WooCommerce, Shopify, EasyOrder, Other) using webhook-based workflows to automate order updates, payment notifications, and customer messaging.

    Design Principles#

    Tenant-based architecture for secure data isolation
    Consistent request and response structures
    Designed for scalable, WhatsApp integrations
    Clear separation between session-based messages and template messages
    All API endpoints are tenant-scoped and protected by secure authentication mechanisms to ensure strict data isolation across tenants.

    Security#

    Responsibility Notice
    RASL provides the technical API layer only. Clients are responsible for message content, user consent, and compliance with WhatsApp and Meta policies.
    Next
    Changelog
    Built with