Smithery is now a part of Arcade.dev! Read more in our announcement here
Reference documentation for Broadcast API (sendbroadcast.net) integration...
Authentication:
Authorization: Bearer YOUR_ACCESS_TOKEN
Base endpoints:
GET /api/v1/broadcasts - List broadcasts
POST /api/v1/broadcasts - Create broadcast
GET /api/v1/broadcasts/:id - Get broadcast
PATCH /api/v1/broadcasts/:id - Update broadcast
DELETE /api/v1/broadcasts/:id - Delete broadcast
POST /api/v1/broadcasts/:id/send_broadcast - Send broadcast
GET /api/v1/subscribers.json - List subscribers
GET /api/v1/subscribers/find.json?email= - Find subscriber
POST /api/v1/subscribers.json - Create subscriber
PATCH /api/v1/subscribers.json - Update subscriber
POST /api/v1/subscribers/unsubscribe.json - Unsubscribe
POST /api/v1/subscribers/resubscribe.json - Resubscribe
Broadcast statuses:
draft | scheduled | queueing | sending | sent | failed | partial_failure | aborted | paused
Read the appropriate reference file based on what you're working on.
401 Unauthorized:
Bearer prefix in Authorization header404 Not Found:
422 Unprocessable Entity:
Body format for broadcasts:
<br> for line breaks, <p> for paragraphs<html>, <head>, <body> tags - Broadcast wraps content automaticallyKey configuration:
{
baseUrl: 'https://your-broadcast-instance.com',
token: 'your_access_token',
fromEmail: 'newsletter@yourdomain.com',
fromName: 'Your Name',
replyTo: 'reply@yourdomain.com'
}
The plugin creates broadcasts in Payload first, then syncs to Broadcast on first update with content (subject + body).
