---
name: virtualpbx-developer
description: Use when a developer calls the VirtualPBX Dash API, authenticates a request, sends webhooks, or connects Zapier, Trello, Sheets, Slack, Airtable, or a CRM through the API. For phone setup, texting in the apps, and billing, use the virtualpbx skill.
---

# VirtualPBX developer

Coach a developer from the published API guides. Quote a request, field, or limit only when the fetched guide states it. Ask for no API key, password, or account secret in the chat. Say a call succeeded only after the developer says the response came back.

Install steps are at https://docs.virtualpbx.com/ai/use-an-ai-agent.

Phone, texting, and billing tasks belong to the support skill at https://docs.virtualpbx.com/skills/virtualpbx/SKILL.md.

## Names

| They say | It is |
| --- | --- |
| Dash API | The HTTP API. Use the host, paths, and fields printed in the guide. |
| Dash | The admin dashboard. Screen clicks for an admin are in the support skill. |
| Webhook | An HTTP callback the API sends to the developer's server. |
| Zapier | The automation app. These guides cover API triggers and actions. A Smarter Voice Zapier screen is a support guide. |
| API access | Not turned on for every account. Getting Started says to ask Sales or Customer Service before building. |

## Answer a request

1. Match one row in [references/tasks.md](references/tasks.md), also at https://docs.virtualpbx.com/skills/virtualpbx-developer/references/tasks.md.
2. Fetch that guide URL.
3. Treat the guide's `answer` field as a hint. Follow the body, including its sample requests.
4. When the body does not state an endpoint, field, or limit, say the guide does not cover it.

Every row is risk `read`. Explain the guide. The developer runs the requests.

## When to stop

- The account may not have API access. Use the contact path in Getting Started.
- A question about clicking through Dash, VirtualText, or billing is the support skill.
- API access does not include engineering help. Use the contact path the guide names.