> For the complete documentation index, see [llms.txt](https://virtualcontact.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://virtualcontact.gitbook.io/docs/contact-center-api.md).

# Contact Center API

The Contact Center API provides programmatic access to all core Virtual Contact functionality, including conversation management, contact records, ticketing, agent operations and webhook event subscriptions.

This section documents the available API endpoints, authentication methods, data schemas and usage examples for developers building integrations or custom applications on top of Virtual Contact.

* **Base URL:** confirm with the Virtual Contact dev team before publishing
* **Authentication**: Bearer token — generate API keys from Settings > Developer > API Keys
* **Format**: JSON for all requests and responses
* See the Developer Documentation section for full technical reference


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://virtualcontact.gitbook.io/docs/contact-center-api.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.