Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.botdog.co/llms.txt

Use this file to discover all available pages before exploring further.

Authenticate your Zap with Botdog using a personal API key from the Botdog dashboard. To use the Botdog Zapier integration, each user must provide their own API key when setting up a Zap. The key identifies your workspace and authorizes the Zap to access your Botdog account. Follow the steps below to obtain and use your key securely.

​
Overview

The Botdog Zapier app uses user-specific API keys for authentication. Every Zap that interacts with Botdog needs a valid key. Requests without a valid key, or with a revoked or mistyped key, return an authentication error. Zapier uses the same API key model as the HTTP API: send the key as the x-api-key header on API calls. For full REST authentication details, see Authentication.

​
How to get your API key

1

Open Botdog on Zapier

Go to Botdog on Zapier and sign in to Zapier (they offer a free trial).
2

Create an API key in Botdog

In the Botdog app, open API settings and create or copy an API key. Keys are prefixed with bd_live_.
3

Connect Botdog in your Zap

When Zapier prompts you to connect Botdog, paste your API key. Complete the connection test, then finish configuring your Zap.
After connecting, you can pick templates or build Zaps from scratch from the Botdog integration page.

​
Security best practices for API keys

  • Treat keys like passwords. Do not share them in chat, tickets, or public repos.
  • Do not embed keys in browser-side code or mobile apps shipped to customers.
  • Rotate keys from the dashboard if they may have been exposed.
  • Prefer a dedicated key for Zapier so you can rotate it without affecting other integrations.
Zapier stores connection credentials according to their security model; you still control issuance and rotation in Botdog. For HTTP error semantics and auth failures, see Errors. For throughput limits, see Rate limiting.