Integrations, API keys and webhooks

Updated October 9, 2026

Connect calendars, data providers and other services to Drop Cowboy® from the Integrations page. For your own code, create API keys and webhooks under Settings.

Connect an integration

  1. Open Settings in the left menu, then click Integrations.
  2. Find the service in its group:
Group What's in it
Compliance & Safety RND (Reassigned Numbers), Black List Alliance (BLA), WebRecon
Contact Data Trestle
Calendars & Conferencing Google Calendar, Microsoft 365, Zoom
Carriers Bring Your Own Carrier
Automation & AI Tools MCP Servers, Bring Your Own LLM
Billing Your subscription billing system, to sync your revenue
SEO & Growth Tools Ahrefs, Google Search Console, Linear
  1. Click the service to open its page.
  2. Connect it the way the page asks:
    • For most services, paste the API key from your account with that service, then click Connect.
    • For Google Calendar, Microsoft 365 and Zoom, click the connect button and sign in to that account.
  3. The service shows Connected when it's done.

Calendar connections belong to you, not the whole team. Each person who takes bookings connects their own calendar.

Not sure what a service needs? Click Ask AI on its row, and the dashboard assistant walks you through it. For carriers, see Bring your own carrier.

If it doesn't work:

  • The service won't connect with your key. Copy a fresh key from your account with that service, paste it again, then click Connect.
  • Your calendar sign-in fails. Sign in to that calendar in the same browser first, then click the connect button again.
  • You don't see Integrations. If you don't see Integrations, ask your account owner for access.

Connect apps without code

Automation is built into your account and connects Drop Cowboy to 700+ other apps, such as HubSpot, Salesforce, Shopify, Calendly and Google Sheets. In an automation, pick In Another App as the trigger, or add Connect Another App as a step. See Build an automation.

Already use Zapier? It still works. To send Drop Cowboy events into a Zap, add a webhook with the URL from the Zap's webhook trigger. To send texts or ringless voicemails from a Zap, the Drop Cowboy app in Zapier asks for a Team ID and a secret. They aren't the pair from API Keys, so contact Drop Cowboy support for them.

Create an API key

An API key lets your own code use the Drop Cowboy API. The API documentation explains every request.

  1. Open Settings in the left menu, then click API Keys.
  2. Click Create API Key.
  3. Name the key after where you'll use it, such as "Website signup form", then click Create.
  4. A green API key created banner appears with API Key and API Secret. Click Copy next to each and store both somewhere safe. The table below never shows the secret.
  5. Click I saved it. The secret will not be shown again.

The secret shows only once. If you miss the banner or lose the secret, create a new key and delete the old one. For AI tools, create keys from Connect AI tools instead, so you can limit what they can do.

The Last Used and Requests columns show how each key is used. To see what your keys have sent, click View Send History. To remove a key, click Delete on its row and confirm. Anything using that key stops working right away.

If it doesn't work:

  • Requests fail with an authentication error. Check you sent both the key and the secret. If you copied the secret wrong, create a new key.
  • Old code uses a Team ID. Keys from API Keys are different from older Classic credentials. Switch that code to the new key and secret, following Authentication.
  • You deleted a key by mistake. Create a new one, then update every place that used the old key.

Add a webhook

A webhook sends events, such as a text failing or a contact replying, to a URL you choose as they happen.

  1. Open Settings in the left menu, then click Webhooks.
  2. Click Add Webhook, or Create Your First Webhook if you have none yet.
  3. In Create a Webhook, fill in Webhook Name and Webhook URL.
  4. Optional: turn on Protect Webhook URL with basic authentication, then fill in the Username and Password your server expects.
  5. Under Events to Send, turn on Subscribe to all events (including future events), or open Select events... and pick only the ones you need.
  6. Click Create.
  7. In the webhook list, click the copy button next to Signing Secret:. Your server uses it to check that each event came from Drop Cowboy.

The Webhooks reference shows how to check the signature and what each event contains.

To change a webhook later, open the menu on its row and click Edit Webhook. If the signing secret leaks, click Regenerate Secret in the same menu and update your server. To stop sending events, click Delete Webhook.

If it doesn't work:

  • Your server receives nothing. Check the Webhook URL can be reached from the internet, then trigger an event again.
  • Your server rejects every event. It's checking with an old secret. Copy the current Signing Secret to your server and try again.
  • You get events you don't want. Click Edit Webhook, remove the extra events under Events to Send, then click Save.

Find an API request

Use the logs when a call to the API didn't do what you expected.

  1. Open Settings in the left menu, then click API Logs. It's also the Logs tab next to API Keys, Webhooks and Canvas.
  2. On Requests, pick request_id or message_id next to Find by ID, paste the value, then click Search.
    • Calls to the REST API return a request_id, in the response body and in the X-Request-Id header.
    • Sends to /rvm, /sms, /voice-broadcast and /ai-broadcast return 202 with a message_id. Search for that value.
  3. Click a row to see the request body, the response body, the validation message, and each attempt to reach the send's callback_url. Failed calls always show a response body. A send row shows the 202 your client received, which is the same whether or not the send passed. A successful REST call shows one only while Store successful response bodies is on.
  4. To narrow the list, use Source, HTTP status, Send result, API key and the date fields. Click Load more for older rows, or Refresh for new ones.

To see only one key's requests, open API Keys under Settings, then click the number under Requests on its row, or click Logs. API Logs opens with that key already chosen.

For REST rows the result is the HTTP status. For send rows it's VALID or INVALID. INVALID rows show the validation message that refused the send. VALID means the send passed the checks made when it arrived. Its final result comes later, on your webhooks, and on the send's callback_url if it had one.

What the logs keep:

  • Request bodies for writes, for sends and for errors. Secrets, tokens and passwords are removed before anything is stored. Long bodies are cut short.
  • Response bodies for errors (HTTP 400 and above) and for every send. To keep what a successful REST call returned too, click Turn on for 7 days next to Store successful response bodies at the top of Requests. It covers requests made after you turn it on, and turns itself off after 7 days.
  • Requests for 14 days.

What the logs don't show:

  • Requests blocked before they reach the API, such as firewall blocks.
  • Requests with an API key Drop Cowboy doesn't recognize, or with no key.
  • Requests to get an OAuth token.
  • Traffic from the dashboard and embedded widgets.
  • Calls to the automation compose route under /agents.

A wrong secret or a missing permission on one of your keys is logged as INVALID, without a request body. Request bodies include the contact details you sent, so only give API Logs access to people who should see them.

If it doesn't work:

  • You can't find a request. Check the ID has no extra spaces, and that the call was less than 14 days ago. A call with a key that isn't one of yours isn't logged.
  • A send says INVALID. Read the validation message in the row. Fix what it names, then send again with a new Idempotency-Key.
  • You don't see API Logs. Ask your account owner for access.

See what your webhook received

Use this to confirm a webhook reached your server, and to see what your server answered.

  1. Open Settings in the left menu, click API Logs, then click Webhooks.
  2. Filter by Webhook, Status, Event type and the date fields.
  3. Click a delivery. Payload sent is the event we posted to your Webhook URL. Response from your endpoint is the status code and body your server answered. The drawer also shows the attempt number, the duration and any error.

The payload is cut off after 8 KB. Some older deliveries have no payload, and the drawer says so. Deliveries are kept for 7 days when they succeeded, 14 days when they failed, and 30 days when they ran out of retries. The log is read-only. You can't resend a delivery from it. To get an event again, trigger it again in your account.

If it doesn't work:

  • A delivery shows an error. Check your server answers within a few seconds with a 2xx status, and that the Webhook URL is reachable from the internet.
  • You can't find a delivery. Check the Webhook and Status filters, and that the event was less than 30 days ago.