Build a Vibrate SMS or WhatsApp integration with ChatGPT, Claude or Cursor in 5 minutes

Most of the time in an SMS or WhatsApp integration isn't spent on code, it's spent reading docs: which endpoint, which fields are required, what an error looks like, how units are counted. The Vibrate API Skill is a single document that answers all of that in a format AI assistants understand. Paste it once, and ChatGPT, Claude, Claude Code, Cursor or GitHub Copilot will write the integration against the real endpoints, without guessing.

What is an AI Skill?

A public Markdown file at a fixed URL that describes the entire Vibrate REST API: authentication, every SMS and WhatsApp endpoint, request and response shapes, Israeli phone-number rules, billing units (256 characters per unit, Hebrew and English priced the same), error codes, and a list of things the API does not do. It follows the SKILL.md convention, so it can also be installed as a local skill in Claude Code.

The file: https://www.vibrate.co.il/vibrate-api-skill.md
Developers page: https://www.vibrate.co.il/en/developers

Step 1: an access key

Create a free Vibrate account, add SMS credits or connect a WhatsApp Business number, and create an access key under Settings → Access Keys. The key goes in the Authorization header of every request.

Step 2: teach the AI the API

Two ways, depending on the tool:

ChatGPT, Claude, Gemini (chat)

Open the file, copy all of it and paste it as the first message. If the tool can open links, the short prompt is enough:

Read https://www.vibrate.co.il/vibrate-api-skill.md and treat it as the authoritative reference for the Vibrate SMS & WhatsApp REST API. Use only the endpoints, fields, status codes and error codes documented there. Then help me with the following task:

Claude Code / Cursor

Install once inside the repo; the skill then loads automatically in every session:

mkdir -p .claude/skills/vibrate-api
curl -fsSL https://www.vibrate.co.il/vibrate-api-skill.md -o .claude/skills/vibrate-api/SKILL.md

In Cursor you can also paste the content into a rule under .cursor/rules; in GitHub Copilot save it as .github/copilot-instructions.md.

Step 3: ask for the integration

Now ask in plain language, for example:

• "Write a Node function that takes a phone number and a message and sends an SMS through Vibrate, handling the insufficient-credits error"
• "After sending, poll delivery status every 20 seconds until all messages are delivered"
• "Send my WhatsApp template with the name and order-number variables to every contact in my distribution list"

Because the AI has read the skill, the code will use POST /v1/sms/send or /v1/sms/sendBulk with the right fields (recipients, message, sender), treat 202 Accepted as "queued and billed" rather than "delivered", and check delivery via GET /v1/sms/run/{runId}/delivery-status.

Example: sending one SMS

curl -X POST https://api.vibrate.co.il/v1/sms/send \
  -H "Authorization: YOUR_ACCESS_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"recipients":["0501231234"],"message":"Hello world","sender":"MySender"}'

The response is a 202 with a runId you use to check delivery. Errors come back with a stable code (for example SMS_INVALID_SENDER or SMS_INSUFFICIENT_CREDITS) and a hints string explaining what to fix.

What the skill prevents

• Invented endpoints: the AI won't try a /v1/sms/status that doesn't exist.
• Phone-format mistakes: the skill explains that Israeli numbers are accepted in any form and normalised server-side.
• Double billing on retry: the AI knows to use Idempotency-Key on sendBulk.
• WhatsApp variable counts: the skill explains that variables are positional and must match the template exactly.

FAQ

Does it work in Hebrew?

Yes. The skill is written in English (where models are most precise on technical docs) but instructs the AI to keep message bodies and explanations in Hebrew when you talk to it in Hebrew.

Is the skill kept up to date?

Yes. It is served from a fixed URL and updated together with the API. Re-fetching it (or re-running the install command) gives you the current version.

Do I need an account to read it?

No. The file and the developers page are public. An account is only needed to create an access key and send messages.

Go to the Vibrate API Skill page