Developer Overview
Driive's developer tools let you go beyond the built-in interface and connect your scheduling platform to the rest of your tech stack. Sync data with your CRM, trigger automations when appointments change, build custom dashboards, or let AI agents manage bookings on your behalf.
Three pillars
Driive's developer platform is built around three core capabilities.
API Keys
API keys give you programmatic access to your Driive data. Use them to read appointment details, create bookings, update customers, and more — all through authenticated HTTP requests. The full REST API is documented in the interactive API reference, generated straight from the API's OpenAPI spec.
Best for: Custom dashboards, data exports, third-party app integrations, and any workflow where you need to pull or push data on demand.
Learn more in API Keys.
Webhooks
Webhooks push real-time notifications to your server whenever something happens in Driive. Instead of polling the API to check for changes, your system receives an HTTP POST the moment a new service request arrives, an appointment is created, confirmed, rescheduled, or cancelled, a customer changes, or an issue lands in your Inbox.
Best for: CRM sync, Slack/email alerts, triggering automations in Zapier or Make, updating external databases, and keeping downstream systems in sync.
Learn more in Webhooks and Webhook Events and Security.
MCP Server
The Model Context Protocol (MCP) server lets AI agents interact with your Driive data using a standardized protocol. Connect tools like Claude, custom AI assistants, or voice-to-booking workflows so they can check availability, create appointments, and look up customers — all without custom API code. The MCP Server is currently in beta.
Best for: AI scheduling assistants, voice-to-booking workflows, automated appointment management, and conversational interfaces for your team or customers.
Learn more in MCP Server.
Where to find developer tools
The Developer section lives in the sidebar under Setup > Developer. You'll see three items:
- Webhooks — Create and manage webhook subscriptions
- API Keys — Generate and manage API keys
- MCP Server — View your MCP endpoint and available tools (beta)
Note: Developer tools are only visible to users with the Admin role. If you don't see the Developer section in your sidebar, ask your organization admin for access.
Common use cases
Here are a few examples of what you can build with Driive's developer tools.
| Use case | Tools |
|---|---|
| Sync new appointments to your CRM (Salesforce, HubSpot, etc.) | Webhooks |
| Send a Slack message when an appointment is scheduled | Webhooks |
| Build a custom reporting dashboard | API Keys |
| Export appointment data to a spreadsheet on a schedule | API Keys |
| Trigger a follow-up email sequence after an appointment completes | Webhooks |
| Let an AI agent check availability and book appointments | MCP Server |
| Voice-to-booking: customer calls, AI handles scheduling | MCP Server + API Keys |
| Push appointment data to your field-service management tool | Webhooks + API Keys |
Getting started
If you're new to Driive's developer tools, we recommend this order:
- API Keys — Start by creating your first API key. You'll need one for API requests and MCP authentication.
- Webhooks — Set up your first webhook to see real-time events flow into your system.
- Webhook Events and Security — Understand the event types and how to verify payloads are authentic.
- MCP Server — Connect an AI agent if you want intelligent scheduling automation.
If you run into issues, check the Troubleshooting guide.