Changelog
Changelog
Changes to the public API at api-v2.dropcowboy.com, newest first.
Versioning policy
- The API is version 2. The version is part of the host
(
api-v2.dropcowboy.com), not the path. - Additive changes ship without notice: new routes, new optional request fields, new response fields, new webhook events and new outcome codes. Build clients that ignore fields and events they don't recognize.
- Breaking changes (removing or renaming a field or route, changing a type, adding a required field, or changing a default) are announced here first, with the date they take effect and what to change.
- The OpenAPI spec and Postman collection change with these pages.
Changes
Delivery status on API log send rows
2026-10-28. GET /register/public/api-logs and
GET /register/public/api-logs/{log_id} now include a delivery object on
send rows: whether the send was refused, still queued, in progress, succeeded,
failed, or mixed, or unavailable when the results couldn't be read and the
request is worth retrying. The single-row route also lists up to 50 recipients. In the
dashboard, Settings > API Logs shows a Delivery column and nudges you to
add a contact.rvm.status / contact.sms.status webhook if you have none.
Campaigns > Show API send history is on by default, and Settings >
API Keys > View Send History is always on that page. Subscribe to the status
webhook (or set callback_url) so your server still gets each result as it
happens. See Where results arrive.
Where send results arrive
Docs only, 2026-10-28. The docs now say where the result of a POST /rvm or
POST /sms send arrives: the status webhook, the send's callback_url, the
contact timeline, and the API entry in Campaigns (Show API send
history is on by default).
The spec now lists the send-result fields on TimelineEntry and log_ids on
API log rows, and shows drop_id as a 24-character hex id. See
Where results arrive.
Phone number reputation
Added POST /phone/public/numbers/reputation, which returns the FCC
unwanted-call complaint counts for up to 100 US or Canadian numbers and costs
$0.001 per number. See Phone number reputation.
Compliance check
Added POST /campaign/public/compliance, which checks an audio_url or a
media_id for compliance problems and costs $0.05 per analysis. A checked
recording also returns the result as compliance on
GET /media/public/media/{media_id}. See
Check audio for compliance.
API access is subject to rate limits and usage policies. API availability, endpoints, and features may change with notice. Breaking changes will be communicated via changelog with migration period when possible. API keys must be kept secure. Customers are responsible for all activity under their API credentials.