Simple REST API for Notifications

Why Developers Choose One-Ping's API

Most notification APIs force you to learn different endpoints, payload formats, and authentication methods for every channel. Want to send a Telegram message? That is one API. Need an email? A different API with different credentials. Slack notification? Yet another SDK to install and configure. One-Ping eliminates all of that complexity by giving you a single, unified REST endpoint that routes your message to any channel you need.

Our API was designed with one principle in mind: if you can make an HTTP POST request, you can send notifications. There are no SDKs to install, no complex OAuth flows to implement, and no channel-specific payloads to memorize. You send JSON in, and notifications go out across Telegram, Email, Slack, Discord, WhatsApp, and SMS.

API Reference: POST /send

The entire One-Ping API revolves around a single endpoint. Here is the full specification for sending a notification.

Endpoint

POST https://api.one-ping.com/send
Content-Type: application/json
Authorization: Bearer YOUR_API_KEY

Request Body Parameters

Code Examples

Here are ready-to-use examples in the most popular languages. Copy, paste, replace your API key, and you are sending notifications in under a minute.

cURL

curl -X POST https://api.one-ping.com/send \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -d '{
    "message": "Your order #1234 has been shipped!",
    "channels": ["telegram", "email"],
    "recipient": "[email protected]",
    "subject": "Order Shipped"
  }'

JavaScript (fetch)

const response = await fetch('https://api.one-ping.com/send', {
  method: 'POST',
  headers: {
    'Content-Type': 'application/json',
    'Authorization': 'Bearer YOUR_API_KEY'
  },
  body: JSON.stringify({
    message: 'Your order #1234 has been shipped!',
    channels: ['telegram', 'email'],
    recipient: '[email protected]',
    subject: 'Order Shipped'
  })
});

const data = await response.json();
console.log(data);

Python (requests)

import requests

response = requests.post(
    'https://api.one-ping.com/send',
    headers={
        'Authorization': 'Bearer YOUR_API_KEY'
    },
    json={
        'message': 'Your order #1234 has been shipped!',
        'channels': ['telegram', 'email'],
        'recipient': '[email protected]',
        'subject': 'Order Shipped'
    }
)

print(response.json())

PHP (cURL)

$ch = curl_init('https://api.one-ping.com/send');

curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_POST => true,
    CURLOPT_HTTPHEADER => [
        'Content-Type: application/json',
        'Authorization: Bearer YOUR_API_KEY'
    ],
    CURLOPT_POSTFIELDS => json_encode([
        'message' => 'Your order #1234 has been shipped!',
        'channels' => ['telegram', 'email'],
        'recipient' => '[email protected]',
        'subject' => 'Order Shipped'
    ])
]);

$response = curl_exec($ch);
curl_close($ch);

echo $response;

Response Format

Every API call returns a consistent JSON response so you always know what to expect. Here is what a successful response looks like.

Success Response (200 OK)

{
  "success": true,
  "id": "msg_a1b2c3d4e5",
  "channels": {
    "telegram": { "status": "sent", "delivered_at": "2025-01-15T10:30:00Z" },
    "email": { "status": "queued" }
  },
  "metadata": {}
}

Error Response (4xx/5xx)

{
  "success": false,
  "error": {
    "code": "INVALID_CHANNEL",
    "message": "Channel 'fax' is not supported."
  }
}

Error Codes

Authentication with API Keys

One-Ping uses Bearer token authentication with API keys. You can generate and manage your API keys from the dashboard. Each key can be scoped to specific channels and has its own rate limits.

Rate Limiting

To ensure fair usage and reliable delivery for all users, the One-Ping API enforces rate limits based on your plan.

When you hit the rate limit, you will receive a 429 response with a Retry-After header indicating how many seconds to wait before retrying. Our automatic retry system handles this gracefully if you have it enabled.

How One-Ping Compares to Other Notification APIs

Traditional notification services require you to integrate multiple APIs, each with their own authentication, payload format, and error handling. Here is how One-Ping stacks up against the alternatives.

Designed for Every Stack

Because One-Ping is a standard REST API with JSON payloads, it works with every programming language, framework, and platform that can make HTTP requests. No vendor-specific SDKs, no dependency bloat.