Skip to main content
For developers

SMS API for Businesses in Israel

A REST API for sending SMS from your own code. Token authentication, one request for a single message or a whole campaign, and delivery reports pushed back to you by webhook. The same API also sends WhatsApp, so there is no second provider to integrate.

First integration in minutesDelivery reports by webhookSMS and WhatsApp in one API

What an SMS API is

An SMS API lets your system send messages without anyone opening a dashboard and pressing a button. Your system notices that something needs a message, calls the API, and the message goes out. It is the difference between a person sending reminders by hand every morning and a reminder that leaves on its own 24 hours before every appointment, including at 3am on a Saturday.

In practice most integrations fall into three groups: verification codes sent the moment a user tries to sign in, operational alerts your system produces (order confirmed, parcel shipped, payment failed), and scheduled reminders derived from data you already hold in a CRM or booking system.

Single message

One POST request with a recipient number and the text. Suited to verification codes and real-time alerts.

Bulk send

A list of recipients in one request, with dynamic fields per recipient. Suited to campaigns and daily reminders.

Scheduled send

The same request with a future timestamp. The message waits in the queue and leaves at the time you set.

How to start

Create an account, generate an API token in the settings, and send one POST request. Every new account is reviewed by us before its first send. The token goes in the Authorization header, and the response comes back as JSON with a message id that you later use to query the delivery status.

The full documentation is on the developers page, with examples for every endpoint. We also publish a reference file in markdown that you can paste straight into Claude, ChatGPT or Cursor, so your coding assistant writes the integration correctly the first time, without guessing field names.

Token authentication

A personal token in the Authorization header. Create and revoke tokens without touching the account password.

Synchronous response

The request returns at once with a message id and an acceptance status, without waiting for delivery on the mobile network.

Reference file for AI

The API documentation in a format you can paste into a coding assistant, so the integration is right from the first attempt.

Delivery reports and what comes back

A successful send and a successful delivery are two different facts, and it is the difference most integrations miss. The API response says we received the message and queued it. What happened next on the mobile network arrives separately, sometimes seconds later and sometimes minutes.

So every message produces status updates you can get in two ways: query the status endpoint with the message id, or register a webhook URL and receive a push on every change of state. If you are building something that depends on delivery, such as holding an account until it is verified, take the update from the webhook and not from the send response.

Query by id

A GET call with the message id returns its current state and the time of the last update.

Webhook

A push to your URL on every change of state, so you do not have to poll in a loop.

Failure reason

A message that was not delivered comes back with a reason, so you can tell a wrong number from a phone that is switched off.

The same API also sends WhatsApp

This is the real difference from SMS-only providers. With most of them SMS is all there is, and if you later want WhatsApp you need a second provider, a second contract, a second token and routing logic of your own to decide who gets what.

At Vibrate the same integration sends SMS and WhatsApp, receives the replies, and can run a chatbot on the conversation. That fits a pattern common to Israeli businesses: send on WhatsApp first, and fall back to SMS only for the people it did not reach. You can build that logic on one API instead of maintaining two separate connections.

What to check before choosing an SMS API provider

Most comparisons between SMS providers stop at the price per message, but when you send through an API a few details affect the cost and the quality of the integration far more than the listed price.

How many characters count as one message

With us it is 256 characters per unit, the same in Hebrew and in English. Other providers count fewer, and a message that looks identical is billed as two units.

Whether delivery reports are real

A provider that returns only an acceptance, and no delivery status, leaves you unable to know whether the customer received it.

What happens when a message fails

Whether you get a failure reason you can act on, and whether you are billed for a message that was not delivered.

Whether you can grow into another channel

If you want WhatsApp a year from now, is that a setting or a new integration project.

Packages and prices

A one-time payment, with no monthly subscription and no commitment. Messages never expire.

100 messages
10₪
0.1 ₪ per message
Buy and start sending
1,000 messages
65₪
0.065 ₪ per message
Buy and start sending
Most popular
5,000 messages
280₪
0.056 ₪ per message
Buy and start sending
10,000 messages
500₪
0.05 ₪ per message
Buy and start sending
25,000 messages
900₪
0.036 ₪ per message
Buy and start sending
50,000 messages
1,500₪
0.03 ₪ per message
Buy and start sending

* All prices include VAT. One billing unit is up to 256 characters, in English and Hebrew alike. Messages never expire, and you can upgrade your package at any time.

FAQ

Questions about the SMS API

A basic send is one POST request and can be working in minutes. A full integration, with delivery reports by webhook, error handling and scheduled sends, usually takes a few hours of work. Every new account is reviewed by us first, and then you create a token and start.

Any system that can send an HTTP request can connect: a website, a CRM, a booking system or an order system. Generate a token in your account, and have your system send a POST request with the recipient's number and the text whenever a message needs to go out. If you write the integration with a coding assistant such as Claude, ChatGPT or Cursor, paste it our reference file. WooCommerce stores have a ready plugin that needs no code.

An operational SMS is a service message that follows from something the customer did: an order confirmation, a shipping update, an appointment reminder or a verification code. A marketing SMS promotes an offer or a product, and under Israel's Communications Law it needs the recipient's explicit consent in advance. The API sends both kinds with the same request and at the same price, and sending promotional content only to people who agreed is the responsibility of the sending business.

With a personal token sent in the Authorization header of every request. You create the token in your account settings, and you can create several tokens and revoke one without affecting the others or changing the account password.

In two ways. You can query a dedicated endpoint with the message id returned by the send response, or register a webhook URL and receive a push on every status change. For flows that depend on actual delivery, such as verifying a user, use the webhook and not the send response, because the send response only says the message was queued.

Yes. Verification codes are one of the most common uses of the API, and the case where speed and accurate delivery reports matter most. Send the code through the API and rely on the webhook update to know whether it arrived before you show the user an error.

It is sent as usual and arrives on the phone as one continuous message, but it is billed in units of 256 characters: up to 512 characters is two units, up to 768 is three, and so on. The count is the same in Hebrew and in English.

Yes. The same integration also sends WhatsApp messages and receives incoming replies, so you can build routing between the channels without connecting a second provider. WhatsApp is priced separately: a monthly subscription plus Meta's fees for template messages.

Yes. You can set a sender ID that shows your business name instead of a phone number. It also applies to messages sent through the API, so a verification code leaving your server reaches the customer under your company's name.

No. The same message package serves both, and the price per unit is the same whether the message was sent from the dashboard, from a scheduled campaign or from an API call. There is no setup fee and no extra charge for API access.

Ready to start sending?

Opening an account takes a minute, with no credit card and no commitment. Once we have reviewed the account you can start sending.

We use cookies that are strictly necessary to run this site, plus analytics cookies to understand how it's used. Analytics cookies are loaded only with your consent, per Israel's Privacy Protection Law. Learn more in our privacy policy