Introduction

Welcome to the APEX Messaging developer hub. Here you’ll find everything you need to integrate SMS, WhatsApp, Telegram, OTP, and webhooks into your applications using our fast, reliable APIs.

Our platform is built for scale, transparency, and control, whether you’re sending your first message or operating at enterprise volume. Each section includes clear explanations, real-world examples, and production-ready code to help you go live quickly.

If you need help, our team is only one call away.

HTTP API Base URL

All HTTP API requests are made to the following base URL:

https://papi.apex-messaging.com

Authentication

APEX Messaging APIs use API key authentication.

Each request must include a valid API key in the apiToken parameter. Requests without a valid key will be rejected.

Creating and Managing API Keys

API keys are managed from the APEX dashboard, under Manage API

From this section, you can:

– Create new API keys
– Enable or disable existing keys
– Delete API Keys that are no longer needed

Creating a New API Key

To generate a new API Key:

1. Navigate to Dashboard → Manage API
2. Enter a name for the API key
3. Specify the allowed IP address(es)
4. Click Add New API

The API key will be displayed once at creation time.
Make sure to copy and store the key securely

API Key Format

API Keys are opaque alphanumeric strings used to authenticate requests.

– The format and length may vary
– keys should be treated as secrets
– Compromised Keys should be terminated immediately

IP Whitelisting

For security reasons, API keys are restricted by IP address.

You must whitelist the IP addresses that will be making API requests. Requests originating from non-whitelisted IPs will be rejected.

Both IPv4 and IPv6 are supported.

Sending an SMS – Basics in Practise

The API supports two request formats:

– GET requests using URL query parameters
– POST requests using JSON payloads

Both methods use the same base URL and API Key.

Example 1: GET Request (URL Parameters)

Suitable for quick testing and simple integrations.

GET https://papi.apex-messaging.com/SendSmsV2
  ?apiToken=YOUR_API_KEY
  &messageType=1
  &messageEncoding=1
  &destinationAddress=35699384535
  &sourceAddress=SENDER1
  &messageText=Hello
  &callBackUrl=https://webhook.site/DLRS
  &userReferenceId=123ABC

Example 2: POST Request (JSON Body)

Recommended for production use and more complex integrations.

Endpoint:

POST https://papi.apex-messaging.com/SendSmsV2

Request body:

[
  {
    "apiToken": "YOUR_API_KEY",
    "messageType": "1",
    "messageEncoding": "1",
    "destinationAddress": "35699999999",
    "sourceAddress": "ABCBank",
    "messageText": "Hello",
    "callBackUrl": "https://webhook.site/DLRS",
    "userReferenceId": "123ABC"
  }
]

What Happens Next

Once authenticated:

– Messages are submitted immediately
– Responses indicate acceptance or rejection of the request
– Callbacks containing delivery receipts (DLRs) are sent back to your “callBackUrl”, if configured, which contain the final delivery status of Delivered, Undelivered or Rejected

Further details for each endpoint, parameter, and response code are covered in the following sections.

Developer