canonical: https://jentic.com/apis/dropcowboy.com/dropcowboy # Drop Cowboy Public API The Drop Cowboy API sends outbound messages across channels: ringless voicemail, SMS and RCS texts, email, voice broadcasts, and AI calls. It manages the contacts, tags, lists, and campaigns behind those sends, rents and configures phone numbers and IVR lines, and builds AI agents that place and handle calls. Sends are asynchronous and return a 202, with results delivered to a callback URL and status webhooks, and the API records consent and maintains a do-not-contact list for compliant outreach. ## For AI agents Send ringless voicemail, SMS and RCS, email, voice broadcasts, and AI calls, and manage the contacts, campaigns, phone numbers, and AI agents behind them. Sends are asynchronous with results delivered to callback URLs and status webhooks. ## Scope Does not handle payment billing, support ticketing, or CRM deal pipelines. Use for outbound multi-channel messaging campaigns and the contacts behind them only. ## Capabilities - Send ringless voicemail, SMS and RCS texts, email, voice broadcasts, and AI calls - Manage contacts with tags, notes, follow-ups, lists, dispositions, and owners - Create and run campaigns, start and pause them, and read their statistics - Rent and configure phone numbers, lines, and IVRs - Build, publish, and manage AI agents that place and handle calls - Record and revoke consent and maintain a do-not-contact list - Read proof-of-delivery receipts and subscribe to status webhooks ## Use cases ### Agent-driven outbound outreach An AI agent connected through Jentic can run a compliant outreach sequence: create a contact, check it against the do-not-contact list, and send a ringless voicemail or text. Because sends return a 202 and report their outcome to a callback URL, the agent can log that a message was queued and later reconcile delivery against the status webhook rather than blocking on the send. Example prompt: Create a contact, confirm it is not on the do-not-contact list, then send a ringless voicemail and record the returned request id. ### Campaign orchestration Drop Cowboy models outreach as campaigns that can be created, started, paused, and measured. An agent can launch a voice broadcast campaign against a contact list, pause it if a budget threshold is hit, and pull campaign statistics to report delivery and response rates back to the operator. Example prompt: Create a campaign, start it against a contact list, then read its statistics and pause it if delivery falls below a threshold. ### Phone number provisioning The phone endpoints search for available numbers, rent them, import numbers a customer already owns, and configure the lines behind them. An agent setting up a new sending identity can search for a number in a given area, rent it, and attach it to a line without a support ticket. Example prompt: Search for an available phone number in a target area code, rent it, and confirm it is listed on the account. ### Consent and compliance tracking Drop Cowboy records per-contact consent and maintains a do-not-contact list, so outreach stays within the rules. An agent can record consent when a contact opts in, revoke it on request, and check any number against the do-not-contact list before a send, keeping a defensible audit trail. Example prompt: Record consent for a contact who opted in, then check their number against the do-not-contact list before sending. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | POST | `/rvm` | Send a ringless voicemail | | POST | `/sms` | Send a text | | POST | `/voice-broadcast` | Send a voice broadcast | | POST | `/ai-broadcast` | Send an AI call | | POST | `/contact/public/contacts` | Create contacts | | GET | `/campaign/public/campaigns` | List campaigns | | POST | `/campaign/public/campaigns/{id}/start` | Start a campaign | | POST | `/phone/public/numbers/rent` | Rent phone numbers | ## Key resources - **Sends** — Send ringless voicemail, SMS and RCS, email, voice broadcasts, and AI calls - **Contacts** — Manage contacts with tags, notes, follow-ups, lists, dispositions, owners, and consent - **Campaigns** — Create, start, pause, and delete campaigns and read their statistics and receipts - **Phone Numbers** — Search, rent, import, and configure phone numbers, lines, and IVRs - **AI Agents** — Create, update, publish, and delete AI agents that place and handle calls - **Compliance** — Record and revoke consent and maintain the do-not-contact list ## 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:** 47 / 100 - **Maturity:** Non-Ready - **Dimensions:** - Foundational Compliance: 27 / 100 - Developer Experience & Jentic Compatibility: 50 / 100 - AI-Readiness & Agent Experience: 47 / 100 - Agent Usability: 55 / 100 - Security: 66 / 100 - AI Discoverability: 79 / 100 - **View full report:** https://jentic.com/apis/dropcowboy.com/dropcowboy/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 Drop Cowboy by hand means sending the x-key and x-secret headers or managing an oauth2 client-credentials token with the right scopes, and handling asynchronous 202 sends whose outcome arrives later on a callback URL and webhooks. Through Jentic you install once, import Drop Cowboy from the API Directory, store the credential once, and your agent calls it. - **Permission scoping:** Drop Cowboy's oauth2 tokens carry per-operation scopes such as contacts:read and campaigns:write, so a rule can grant your agent only the scopes it needs. You choose the operations it may call, so send scopes like ringless voicemail or text are not included unless you add them. - **Credential handling:** Your Drop Cowboy API key and secret, and any oauth2 token, are stored encrypted by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'send a ringless voicemail' or 'start a campaign', and Jentic returns the matching Drop Cowboy operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Twilio** — Twilio sends SMS and places voice calls across a broad programmable-communications platform - **Plivo** — Plivo offers SMS and voice calling as a direct alternative to Drop Cowboy's text and call sends - **Telnyx** — Telnyx provides carrier-grade numbers and voice that can underpin an outreach stack alongside Drop Cowboy - **Mailchimp** — Mailchimp runs email marketing campaigns that complement Drop Cowboy's voice and text outreach ## FAQ ### What authentication does the Drop Cowboy API use? Per its OpenAPI spec, Drop Cowboy accepts an API key and secret sent as the x-key and x-secret headers, or an oauth2 client-credentials bearer token whose scopes each operation lists, with additional bearer JWT schemes for portal and embed contexts. A request satisfies auth by presenting the key-and-secret pair or a scoped token. Through Jentic these credentials are stored encrypted by your own Jentic One instance and injected at call time, so they never reach the agent's context. ### Is there a Drop Cowboy MCP server? You don't need an MCP server to give your agent the Drop Cowboy API. Jentic connects it directly from the API Directory: import Drop Cowboy, store your key and secret once, and your agent calls its operations. Operations are discovered on demand, so no extra server's tool definitions are loaded into the agent's context. ### Can I limit what my agent is allowed to do with the Drop Cowboy API? Yes. Drop Cowboy's oauth2 tokens carry per-operation scopes, so you can write a rule that grants only the ones your agent needs, such as contacts:read for lookups, while withholding send scopes. Combined with Jentic rules you can allow the read and campaign-status operations but keep ringless voicemail and text sends out of reach unless you add them, and every call the agent makes is logged. ### Can I send a ringless voicemail with the Drop Cowboy API? Yes. The ringless voicemail send endpoint accepts the recipient and media and returns a 202, meaning the request was accepted; the actual result arrives on your callback URL and status webhooks, so a 202 does not by itself mean the send succeeded. The same asynchronous pattern applies to the SMS, voice broadcast, and AI call sends. ### What are the rate limits for the Drop Cowboy API? The OpenAPI spec does not publish numeric rate limits; it instructs clients to branch on the HTTP status and retry 429 and 5xx responses with exponential backoff and jitter. Check the Drop Cowboy developer documentation for the current limits before running high-volume campaigns. ### How do I send a text with the Drop Cowboy API through Jentic? Install Jentic One, import Drop Cowboy from the API Directory, and store your API key and secret once. Your agent then searches by intent, for example 'send a text', and Jentic returns the matching send operation with its input schema. To run it on your own infrastructure, install Jentic One from its GitHub repo.