NOTIFICATIONS FOR DEVELOPERS

Your app.
Your events.
WhatsApp notifications.

Add order updates, appointment reminders and documents to your software. Send through a REST API and receive replies and delivery events in your backend.

20 messages a day · No card required · Your own number

APP EVENT → WHATSAPP NOTIFICATION
o.Your applicationExample
POST /v1/messages
{
  "channel": "whatsapp",
  "to": "+13015550123",
  "text": "Your appointment is confirmed!"
}
Your backend decides when to notify.
O
Your business

Your appointment is confirmed!

Example message
API → WhatsApp → your customer
Illustration. Does not show live activity.
↗

Your numberOne connection per account

⌘

Your integrationAPI and signed webhooks

◎

Your controlSeparate keys and connection

BUILD YOUR FIRST NOTIFICATION

An event in your app. A useful update for your user.

For SaaS products, CRMs, booking systems and internal tools.

01

Create your workspace

Register your project and store your API key in your backend. Your trial starts when you create your account.

02

Connect your WhatsApp

Scan your QR code from Linked devices. You can change numbers while keeping one active line.

03

Trigger from your backend

Call the API when an order, appointment or service changes. Store the message ID and follow its status through signed webhooks.

WHAT WILL YOU BUILD?

Built around your application events.

order.paid

Order confirmations

Confirm a purchase or send an invoice after your application records a payment.

appointment.confirmed

Appointments & reminders

Notify your users when a booking is confirmed or changed.

service.completed

Reports & documents

Share a service photo or a PDF report from your own application.

ticket.updated

Support updates

Let users know a ticket changed, and receive their replies in your backend.

These are example events in your software. Your backend schedules and triggers the API call; OswiLink does not monitor your orders or bookings.

REST API · JSON · WEBHOOKS

Your first notification starts here.

Use cURL, Node.js or Laravel from your backend. Keep one idempotency key per notification and store the returned message ID.

POST /v1/messages
curl "https://oswilink.com/v1/messages" \
  -H "Authorization: Bearer $OSWI_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: order-123-confirmed-v1" \
  --data '{"channel":"whatsapp","to":"+13015550123",
    "text":"Your order is confirmed."}'

Example only. Replace the fictional recipient with an authorized test number. HTTP 202 means queued; follow the message status to confirm delivery. Live sending requires activation during the beta.

SEND THE CONTEXT YOUR USERS NEED

A notification.
With the right attachment.

Send a service photo, an invoice PDF or a text update from the same endpoint. Files are supplied through your public HTTPS URLs.

See formats and limits
AaText▧Images▷Video≈AudioPDFDocuments↩Replies
DEVELOPER BETA

Build one workflow.
Test it end to end.

7days free
  • 20 messages a day during your trial
  • One WhatsApp line per account
  • API key, QR code and documentation
  • No card or automatic charges
Pilot access

Live sending requires operator activation. Simulation mode does not send messages to phones. The connection uses Baileys and is not the official WhatsApp API.

Give your application a notification channel.

Create an account, save your backend key and open the integration guide.

Google sign-in is coming soon.

or with your email and password
NO HIDDEN FINE PRINT

Before you start.

Can I use it from a mobile app or any backend?

Any backend that can make HTTPS requests can use the REST API. A mobile or browser app should call your backend so that your private API key stays on the server.

Can each of my customers connect their own number?

The beta supports one active WhatsApp number per OswiLink account. A reseller dashboard, multiple customer numbers in one account and customer provisioning by API are not available yet.

Do I need my own phone?

Yes. You link a WhatsApp account already registered on your phone. OswiLink does not create the account or replace that registration.

What happens when my trial ends?

New sends are blocked and the connection stops. There are no automatic charges. Monthly subscriptions and payments are not active yet.

Are my conversations stored?

We are not a permanent archive. Content and events are kept temporarily for about 24 hours; technical message metadata for up to 30 days. Connection credentials are stored separately. Read the details.

How does OswiLink connect to my WhatsApp?

Link your WhatsApp account by scanning a QR code from Linked devices. Then manage your connection and reconnect when needed, all from your dashboard. OswiLink is an independent service and does not use the official WhatsApp Business Platform.