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

# Introduction

> The Sales Ask API lets you pull call recordings, push appointments, and receive webhook events when recordings are processed.

## What you can do

The API is organized around three main resources:

<CardGroup cols={3}>
  <Card title="Recordings" icon="microphone" href="/api-reference/recordings/list-recordings">
    Pull processed recordings with AI-generated notes, summaries, coaching, and action items.
  </Card>

  <Card title="Scheduled tasks" icon="calendar" href="/guides/scheduled-tasks">
    Push upcoming appointments so Sales Ask can match them to recordings after the call.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/guides/webhooks">
    Subscribe to `recording.processed` and `recording.integration_updated` events to get notified when recordings are analyzed or synced to a CRM.
  </Card>
</CardGroup>

## Authentication

Every request requires your organization API key in the `x-api-key` header. Keys are scoped to an organization — all data returned is filtered to your organization automatically.

```bash theme={null}
x-api-key: <your-api-key>
```

API keys are generated by admins in the Sales Ask app under **Settings → Organization → Organization API Key**. See [Quickstart](/quickstart) for step-by-step instructions.

## Base URL

```
https://integrations.salesask.com
```

## Response format

All endpoints return JSON. Successful responses use HTTP `200` with a top-level key matching the resource name. Errors return an appropriate HTTP status code with a `message` field.

```json theme={null}
{ "message": "Recording not found" }
```

## Timestamps

All timestamps are returned as ISO 8601 strings in UTC, for example `2026-03-01T14:22:00.000Z`.

Duration fields (such as `duration`, `avgDurationMs`) are in milliseconds.