canonical: https://jentic.com/apis/slybroadcast.com/slybroadcast # Slybroadcast API Slybroadcast provides a ringless voicemail delivery service. The API allows sending voicemail campaigns, managing campaigns (pause, resume, stop, cancel), retrieving campaign results and reports, managing audio files, and maintaining a Do Not Dial list. All campaign and management requests go to the /vmb.php endpoint via POST with form data. Different operations are distinguished by the c_option o. The API exposes 3 endpoints. ## For AI agents Programmatically campaign operations, list audio files. Covers 3 operations. ## Scope Does not handle payments, crm, or developer tools - use for communications only. ## Capabilities - Campaign Operations - List Audio Files - Download Audio File - Query and filter Slybroadcast API records by parameters - Monitor Slybroadcast API operational status and events ## Use cases ### Communications Operations Use the Slybroadcast API to perform communications operations programmatically. The API provides 3 endpoints covering core functionality including campaign operations, list audio files, download audio file. Example prompt: Call POST /vmb.php to campaign operations ### Automated Campaigns Management Automate campaigns operations by combining multiple Slybroadcast API endpoints. Agents can list audio files and then download audio file in a single workflow. Example prompt: Call POST /vmb.aflist.php to list audio files, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Slybroadcast API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle none tokens manually. Example prompt: Search Jentic for 'campaign operations', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/vmb.php` | Campaign Operations | | POST | `/vmb.aflist.php` | List Audio Files | | POST | `/vmb.dla.php` | Download Audio File | ## Key resources - **Campaigns** — Send and manage ringless voicemail campaigns, retrieve results, and manage Do Not Dial lists. - **Audio** — List and download audio files for voicemail campaigns. ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 74 / 100 - **Maturity:** AI-Aware - **Dimensions:** - Foundational Compliance: 100 / 100 - Developer Experience & Jentic Compatibility: 56 / 100 - AI-Readiness & Agent Experience: 56 / 100 - Agent Usability: 94 / 100 - Security: 100 / 100 - AI Discoverability: 100 / 100 - **View full report:** https://jentic.com/apis/slybroadcast.com/slybroadcast/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring Slybroadcast by hand means posting form credentials to its gateway at mobile-sphere.com, parsing its non-JSON responses, and managing retries yourself. Through Jentic you install once, import the Slybroadcast API from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** Slybroadcast sends targets in the request body rather than the URL path, so scope the agent to the operations it needs, such as posting a voice broadcast or listing audio files. You choose which operations are allowed, so the delivery-report call is not included unless you add it. - **Credential handling:** Your Slybroadcast credential is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send a voicemail broadcast' or 'list my audio files', and Jentic returns the matching Slybroadcast operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Twilio** — Alternative communications API - **Sendgrid** — Alternative communications API - **Pusher** — Complementary communications API ## FAQ ### What authentication does the Slybroadcast API use? The Slybroadcast API uses no authentication. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I campaign operations with the Slybroadcast API? Yes. Use the POST /vmb.php endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Slybroadcast API? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I campaign operations through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'campaign operations'. Jentic returns the matching Slybroadcast API operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Slybroadcast API have? The Slybroadcast API exposes 3 endpoints covering campaigns, audio operations. ### Can I limit what my agent is allowed to do with the Slybroadcast API? Yes. Because you run Jentic One yourself, you decide which Slybroadcast operations your agent may call and which credential it uses. You can allow just the operations it needs, such as posting a voice broadcast (POST /vmb.php) or listing audio files (POST /vmb.aflist.php), and leave the download audio file and campaign result operations out unless you add them. Your own rules govern every call, so the agent cannot reach an endpoint you have not granted.