Webhooks & HTTP Integrations
Connect Israelnumber services to your own backend. Forward inbound SMS to an HTTP endpoint through the documented SMS Config API or the account portal, and use the documented DID API to provision numbers and configure supported forwarding destinations.
What Is Available Today
Israelnumber supports inbound SMS-to-webhook forwarding as a documented API capability. Configure the destination programmatically through POST /api/sms using the webhook_url field, or configure the same destination in the account portal under Forward Type → API. When an SMS arrives, the platform replaces the supported placeholders with the live sender, message text, and destination number and requests your URL.
The supplied Postman API reference also documents DID provisioning and forwarding-management calls. It does not document a generic call-event webhook system with events such as incoming_call, call_answered, or call_ended, so this page does not advertise those events as production API features.
Webhook & Integration Reference
A clear distinction between documented API functionality, portal configuration, and unsupported generic event callbacks.
| Capability | How It Works | Status |
|---|---|---|
| SMS → Webhook | Configure the webhook destination through POST /api/sms using webhook_url, or set the same destination under Forward Type → API in the account portal. | Available now |
| SMS webhook configuration via API | Programmatically assign or change the SMS webhook URL through POST /api/sms using the documented webhook_url field. | Documented API |
| DID provisioning & forwarding | Use the documented API calls to list, assign, manage, configure forwarding for, and release virtual numbers. | Documented API |
| Generic call-event webhooks | Named lifecycle callbacks such as incoming_call, call_answered, and call_ended are not defined in the supplied Postman reference. | Not documented |
Inbound SMS → Webhook
Configure the destination programmatically through POST /api/sms using webhook_url, or set the same destination in your Israelnumber account under Forward Type → API. Include the placeholders exactly as shown, including the curly braces.
API configuration example:
POST https://newsip.israelnumber.com/api/sms
x-auth-token: YOUR_SESSION_X_AUTH_TOKEN
Content-Type: application/json
{
"action": "add",
"id": "YOUR_ACCOUNT_ID",
"token": "YOUR_ACCOUNT_TOKEN",
"did": "YOUR_SMS_ENABLED_DID",
"webhook_url": "https://example.com/israelnumber/sms?from={CallerID}&text={SMS_TEXT}&to={SMS_DST_ADDR}"
}dest_sms and dest_email may be omitted. Use the generated session x-auth-token returned after Login for the x-auth-token request header.Webhook URL template:
https://example.com/israelnumber/sms?from={CallerID}&text={SMS_TEXT}&to={SMS_DST_ADDR}{CallerID} = sender phone number · {SMS_TEXT} = SMS message content · {SMS_DST_ADDR} = Israelnumber destination number. URL-encode values correctly in your application before further processing or storage.Example request after placeholder replacement:
https://example.com/israelnumber/sms?from=1234567890&text=Hello&to=0987654321Node.js / Express endpoint example:
// npm install express
const express = require("express");
const app = express();
app.get("/israelnumber/sms", (req, res) => {
const sender = req.query.from;
const message = req.query.text;
const destination = req.query.to;
console.log("Inbound SMS", {
from: sender,
to: destination,
text: message
});
// Your logic here:
// - create a CRM ticket
// - trigger an automation
// - send the message to an AI workflow
// - store it in your application
res.status(200).send("OK");
});
app.listen(3000, () => console.log("Listening on port 3000"));Voice Routing Is Different from SMS Webhooks
The documented DID API can be used to provision numbers and change supported call-forwarding destinations. The supplied API example demonstrates call_type=2 with a trunk IP in call_type_value.
Do not treat that forwarding API as proof of a generic HTTP call-event webhook or live voice-media webhook. Those capabilities are not defined in the supplied Postman reference. Use only forwarding destination types supported by your Israelnumber account and telephony setup.
More API Guides
|
| ||||
|
|
FAQ — Webhooks
Can incoming SMS be forwarded to my webhook?
Yes. Configure the destination programmatically through POST /api/sms using webhook_url, or open the SMS forwarding settings in the account portal, select Forward Type → API, and enter a URL containing {CallerID}, {SMS_TEXT}, and {SMS_DST_ADDR}. Israelnumber replaces those placeholders with live values when the message is forwarded.
Can I configure the SMS webhook URL through the API?
Yes. The supplied Postman API documents SMS webhook configuration through POST /api/sms using the webhook_url field. The same destination can also be configured in the account portal under Forward Type → API.
Does Israelnumber provide incoming_call, call_answered, and call_ended webhook events?
Those generic event names and payload structures are not documented in the supplied Postman API reference, so they should not be relied on as documented production features.
Can I connect a virtual number to an AI voice agent?
Yes, when the AI platform can receive calls through a compatible forwarding destination supported by your Israelnumber account and telephony setup. The supplied API example demonstrates forwarding to a trunk IP. This is separate from the SMS-to-webhook feature described on this page.
Build HTTP Integrations with Israelnumber
Use the documented SMS-to-webhook API today together with the DID provisioning and forwarding APIs.