Simple GET API Test

Complete the test fields to generate the production GET URL.

Your WhatsApp Sender IDs

Only sessions belonging to this customer account are shown.
Use sessionId, instanceId, or senderNumber to select the sending WhatsApp account.

API IP Security

Production Base URL

https://alert.365services.in

Authentication And Customer Isolation

Recommended for every API: x-api-key: YOUR_KEY
GET URL option: apikey=YOUR_KEY
AlertHub-compatible option: apipassword=YOUR_KEY

Each API key is permanently scoped to one customer account.
Sender sessions, plan limits, IP rules, queues, duplicate checks, and message logs are filtered by that customer ID.
A sessionId, instanceId, or senderNumber belonging to another customer is rejected and no other customer details are returned.

List Your Sender Sessions

GET https://alert.365services.in/api/v1/sessions
Header: x-api-key: YOUR_KEY

Response:
{
  "sessions": [
    {
      "sessionId": "SESSION_ID",
      "instanceId": "INSTANCE_ID",
      "displayName": "Main WhatsApp",
      "senderNumber": "SENDER_NUMBER",
      "status": "connected",
      "liveConnected": true
    }
  ]
}

Sender Selection

sessionId: 365Alert WhatsApp session ID
instanceId: AlertHub-compatible instance ID
senderNumber: Connected WhatsApp number with country code

If exactly one sender is connected, sender selection is optional.
If more than one sender is connected, provide one selector.
If multiple selectors are provided, all must identify the same sender.

Recommended: Stable Sender Number

Use senderNumber alone in external applications, with country code and digits only using your linked WhatsApp number. Keep using the same customer API key.

• Show QR / reconnect keeps the existing sessionId and instanceId.
• Delete and recreate can change session IDs. senderNumber keeps working after the same number is linked again under your customer account.
• If you provide both senderNumber and sessionId, both must match the same session. A mismatch returns HTTP 400; an old ID is not ignored.
• Your API key limits sender selection to your own customer account.
• A disconnected number must be relinked before sending.

For strict session validation, include sessionId and update it after deletion and recreation. To avoid this update, omit sessionId and instanceId from your external integration.

Required Safe Send Field

Every send request must confirm recipient consent:
GET APIs: add &optIn=true
POST JSON API: add "optInConfirmed": true

If optIn=false, missing, 0, no, or off:
Message will not send and API returns FAILED.

Customer Safety Setting

Duplicate block time is available in API Security.
Allowed value: 0 to 720 hours
0 disables duplicate blocking for this customer.
Customer value overrides the admin platform default.

Two API Message Delivery Rule

Case 1: Same number + same message + within duplicate block time
First API call: delivered if WhatsApp session is live
Second API call: blocked as duplicate

Case 2: Same number + different message
First API call: delivered if WhatsApp session is live
Second API call: queued and auto-sent after sender cooldown, minimum 5 seconds

Case 3: Different number + same message
Both can deliver. Fast calls are queued and sent one by one with the 5 second cooldown

Case 4: optIn=false on any request
That request is blocked before sending.

HTTP Send URL

GET https://alert.365services.in/api/send?apikey=YOUR_KEY&senderNumber=SENDER_NUMBER&sendto=RECIPIENT_NUMBER&content=hello&requestid=trx_001&optIn=true

HTTP Send URL Options

Authentication: apikey or x-api-key header
Sender: sessionId, instanceId, or senderNumber
Recipient: sendto or to (8 to 15 digits with country code)
Message: content or message (required, maximum 1500 characters)
Reference: requestid or requestId (optional)
Consent: optIn, optInConfirmed, recipientConsent, or consent (must be true/1/yes/on)
URL encode all query-string values, especially message content.

AlertHub Style API

GET https://alert.365services.in/api/AlerthubService/SendMessage?apiuserid=YOUR_USER_ID&apipassword=YOUR_KEY&instanceId=INSTANCE_ID&requestid=trx_001&sendto=RECIPIENT_NUMBER&messagetype=text&content=hello&optIn=true

Lowercase alias:
GET https://alert.365services.in/api/alerthub/SendMessage

AlertHub API Options

apiuserid: Compatibility value; API ownership is determined by apipassword
apipassword: Customer API key (required unless x-api-key header is used)
Sender: instanceId, sessionId, or senderNumber
requestid: Your optional transaction/reference ID
sendto: Recipient number with country code (required)
messagetype: text (current supported type)
content: Text message (required, maximum 1500 characters)
Consent: optIn, optInConfirmed, recipientConsent, or consent (required)

REST JSON API

POST https://alert.365services.in/api/v1/messages/send
Content-Type: application/json
x-api-key: YOUR_KEY

{
  "senderNumber": "SENDER_NUMBER",
  "to": "RECIPIENT_NUMBER",
  "content": "hello",
  "requestId": "trx_001",
  "optInConfirmed": true
}

REST JSON API Options

Sender: sessionId, instanceId, or senderNumber
Recipient: to or sendto (required, 8 to 15 digits with country code)
Message: content or message (required, maximum 1500 characters)
Reference: requestId or requestid (optional)
Consent: optInConfirmed, optIn, recipientConsent, or consent (must be true/1/yes/on)

Success Response

HTTP 202
{
  "statusCode": 1,
  "status": "SENT",
  "message_id": "WHATSAPP_PROVIDER_MESSAGE_ID",
  "tid": 123456,
  "requestId": "trx_001",
  "sessionId": "SESSION_ID"
}

Queued Response

HTTP 202
{
  "statusCode": 2,
  "status": "QUEUED",
  "message_id": "",
  "tid": 123456,
  "requestId": "trx_002",
  "sessionId": "SESSION_ID",
  "queued": true,
  "description": "Message queued. Estimated send after 5 second(s)."
}

AlertHub Style Success Response

HTTP 202
{
  "statusCode": 1,
  "status": "SENT",
  "description": "Message Sent -> ID : WHATSAPP_PROVIDER_MESSAGE_ID",
  "message_id": "WHATSAPP_PROVIDER_MESSAGE_ID",
  "broadcasttime": "18/8/2026, 10:30:00 pm",
  "tid": 123456
}

AlertHub Style Queued Response

HTTP 202
{
  "statusCode": 2,
  "status": "QUEUED",
  "description": "Message queued. Estimated send after 5 second(s).",
  "message_id": "",
  "broadcasttime": "18/8/2026, 10:30:00 pm",
  "tid": 123456
}

Error Response

HTTP 400 / 401 / 403 / 429
{
  "statusCode": -1,
  "status": "FAILED",
  "message": "Reason of failure"
}

AlertHub style errors use "description" instead of "message":
{
  "statusCode": -1,
  "status": "FAILED",
  "description": "Reason of failure",
  "tid": null
}

Response Field Meaning

statusCode: 1 means sent, 2 means queued, -1 means failed
status: SENT, QUEUED, or FAILED
message_id: WhatsApp provider message id
tid: 365Alert tracking id for support/log search
requestId: Your own transaction/reference id
sessionId: WhatsApp session used for sending
queued: true means accepted and waiting for cooldown
error: Machine readable error code on dashboard/customer routes
message / description: Human readable failure reason

Common Error Values

HTTP 400 - Send request failed
sendto must be a valid phone number with country code.
Message content is required.
Recipient opt-in confirmation is required before sending.
Message content is too long for safe sending. Keep it under 1500 characters.
Public API sends during cooldown return QUEUED and auto-send after cooldown.
Duplicate message already sent to this recipient within N hour(s).
No connected WhatsApp session found. Scan QR first.
WhatsApp session is not connected. Scan the QR first.
Multiple WhatsApp senders are connected. Specify sessionId, instanceId, or senderNumber.
Selected sender was not found or is not connected to this customer account.
senderNumber must contain a valid phone number.
Plan expired. Renew first.

HTTP 401 - Authentication failed
invalid_api_key: Missing or invalid API key.

HTTP 403 - Access blocked
customer_disabled: Customer account is not active.
ip_not_allowed: Request IP is not allowed.

HTTP 429 - Rate limited
rate_limited: Too many requests. Try again later.

HTTP 404 - Wrong URL
not_found: Route not found.

Payment Requests