> ## Documentation Index
> Fetch the complete documentation index at: https://docs.brightalk.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Brightalk API introduction

> Connect company systems to Brightalk AI calling with the server-to-server Public API.

Brightalk Public API connects the software your company already uses—such as a CRM, form, ERP, or internal workflow—to AI calling. Your server can create contacts, select an eligible AI voice agent, place one call, start batch dialing, or create an Automation run from a dashboard-managed Automation.

Create a scoped API key in [Brightalk API settings](https://www.brightalk.ai/settings/integrations/api), keep it on your server, and call `https://api.brightalk.ai`. Every accepted call or workflow returns an API resource that you can retrieve until it reaches a terminal status.

AI voice agents and Automations are configured and managed in the Brightalk dashboard. Calls created through this API are AI-mode calls only.

## Choose an execution path

<CardGroup cols={3}>
  <Card title="One AI call" icon="phone" href="/en/guides/place-one-call">
    Queue one immediate asynchronous call with an eligible AI voice agent, then retrieve its result.
  </Card>

  <Card title="Batch dialing" icon="list" href="/en/guides/create-start-batch">
    Create a draft for up to 1,000 unique recipients, then start, schedule, and control it.
  </Card>

  <Card title="Automation run" icon="diagram-project" href="/en/guides/run-automation">
    Create a run from an active dashboard-managed Automation for one contact, then track it.
  </Card>
</CardGroup>

## What the API covers

The API provides organization-scoped contacts, an eligible agent catalog, direct calls, batches, Automation summaries, and Automation runs. Accepted execution work is asynchronous: a success response creates or returns an API resource that your server retrieves until it reaches a terminal status.

Capabilities outside the documented contract are not supported. See [Availability](/en/availability) for the explicit boundary and dashboard dependencies.

## Next step

Follow the [Quickstart](/en/quickstart) to create a scoped key, queue one call, and interpret the result.