Skip to main content

sendblue-api

Integrates with Sendblue API to send and receive iMessages, SMS, and RCS messages programmatically, enhancing messaging capabilities.

Install this skill

or
24/100

Security score

The sendblue-api skill was audited on Jun 1, 2026 and we found 20 security issues across 2 threat categories. Review the findings below before installing.

Categories Tested

Security Issues

medium line 52

Curl to non-GitHub URL

SourceSKILL.md
52curl -X POST https://api.sendblue.com/api/send-message \
medium line 3

Webhook reference - potential data exfiltration

SourceSKILL.md
3description: "Send and receive iMessage, SMS, and RCS from application code via the Sendblue HTTP API — text, media, group messages, send styles, reactions, typing indicators, status callbacks, and in
medium line 10

Webhook reference - potential data exfiltration

SourceSKILL.md
10tags: [sendblue, imessage, sms, rcs, messaging, api, webhooks]
medium line 22

Webhook reference - potential data exfiltration

SourceSKILL.md
22Sendblue is a REST API that sends iMessage (blue bubbles), SMS, and RCS from a provisioned phone number. Everything is plain JSON over HTTPS — no SDK is required. The API covers outbound 1:1 and group
medium line 27

Webhook reference - potential data exfiltration

SourceSKILL.md
27- Use when receiving inbound messages via webhooks.
medium line 71

Webhook reference - potential data exfiltration

SourceSKILL.md
71Configure webhook URLs in the dashboard or via `POST /api/account/webhooks`. Sendblue POSTs JSON to your endpoint. Respond with 2xx promptly — non-2xx triggers retries and duplicate deliveries. Event
medium line 89

Webhook reference - potential data exfiltration

SourceSKILL.md
89| POST | `/api/account/webhooks` | CRUD webhook subscriptions |
medium line 135

Webhook reference - potential data exfiltration

SourceSKILL.md
135### Example 4: Inbound webhook payload (`receive`)
medium line 157

Webhook reference - potential data exfiltration

SourceSKILL.md
157- ✅ **Return 2xx fast from your webhook**, then process async. Non-2xx triggers duplicate deliveries.
medium line 174

Webhook reference - potential data exfiltration

SourceSKILL.md
174- Treat every outbound send, contact/webhook mutation, read receipt, reaction, or typing indicator as state-changing. Preview the recipient, sender line, content, and callback/webhook changes, then wa
medium line 175

Webhook reference - potential data exfiltration

SourceSKILL.md
175- Webhook endpoints should be on HTTPS and idempotent — same `message_handle` may arrive more than once.
medium line 185

Webhook reference - potential data exfiltration

SourceSKILL.md
185- **Media URLs expire in ~30 days.** If you need durable media from inbound webhooks, download and re-host on receipt.
medium line 187

Webhook reference - potential data exfiltration

SourceSKILL.md
187- **Webhook retries on non-2xx.** Return 200 even when you've decided to ignore the event; otherwise expect duplicate deliveries.
medium line 199

Webhook reference - potential data exfiltration

SourceSKILL.md
199- Useful undocumented-here features: carousels (`/api/send-carousel`), FaceTime/contact-card sharing, advanced webhook filtering, contacts API beyond basic CRUD — see the docs site.
low line 36

External URL reference

SourceSKILL.md
36https://api.sendblue.com
low line 52

External URL reference

SourceSKILL.md
52curl -X POST https://api.sendblue.com/api/send-message \
low line 101

External URL reference

SourceSKILL.md
101"media_url": "https://example.com/img.jpg",
low line 103

External URL reference

SourceSKILL.md
103"status_callback": "https://yourapp.com/sendblue/status"
low line 141

External URL reference

SourceSKILL.md
141"media_url": "https://...",
low line 198

External URL reference

SourceSKILL.md
198- Sendblue: <https://sendblue.com>
Scanned on Jun 1, 2026
View Security Dashboard
Installation guide →