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

# Quickstart (v1)

> One curl call, your Group ID, and an API token — your first Operata API response in 90 seconds.

Send one curl request and see an Operata contact in the v1 format. For the v2 data model, use the [Quickstart](https://docs.operata.com/docs/quickstart.md). You need a Group ID, an API token, and curl.

## Before you start

* An [Operata account](https://app.operata.io). Your **Operata Group ID** is the UUID in the console URL.
* An **API token** generated under **Settings → Config → API**.

## Make the request

```bash theme={null}
curl -u "$OPERATA_GROUP_ID:$OPERATA_API_TOKEN" \
  "https://api.operata.io/v1/data/calls?fromTime=2026-05-17T00:00:00Z&toTime=2026-05-18T00:00:00Z&size=1"
```

## What you should see

A JSON array with one contact. This example is shortened:

```json theme={null}
[
  {
    "softphoneSummary": {
      "contactId": "56f36f8c-463e-44fe-aff7-54ea7533cec1",
      "agentUserName": "agent_42",
      "agentCity": "Melbourne",
      "networkType": "wlan",
      "networkPerformanceMetrics": {
        "jitter": { "min": 1, "avg": 2, "max": 4 },
        "rtt": { "min": 20, "avg": 32, "max": 36 },
        "mos": { "min": 4.41, "avg": 4.42, "max": 4.42 }
      }
    },
    "contactDurationSummary": {
      "contactDurationRoundedMin": 1,
      "contactDurationActualSec": 19
    }
  }
]
```

## What the response means

* You authenticated with HTTP Basic — Group ID as username, token as password. See [Authentication](https://docs.operata.com/docs/api-authentication.md).
* You requested one contact from a 24-hour window using the contact summary endpoint. See [List contact summaries](https://docs.operata.com/docs/api-contact-summary.md).
* The response is a plain JSON array. The `RecordCount` response header holds how many contacts match in total, and you page with `from` and `size`. See [Pagination](https://docs.operata.com/docs/api-pagination.md).
* A 429 response means you hit the per-token budget — back off using `Retry-After`. See [Rate limits](https://docs.operata.com/docs/api-rate-limits.md).
* Errors come back as an HTTP status code with a short plain-text body. See [Errors](https://docs.operata.com/docs/api-errors.md).

## Related

> **[Concepts](https://docs.operata.com/docs/concepts-customer-journey-trace.md)**
>
> The mental model behind contacts, signals, and observations.

> **[API reference](https://docs.operata.com/docs/api-getting-started-v1.md)**
>
> Every endpoint, every parameter.

> **[Data redaction](https://docs.operata.com/docs/api-data-redaction.md)**
>
> Choose which fields to strip before they reach Operata.


## Related topics

- [Getting started with the Operata API (v1)](https://docs.operata.com/docs/api-getting-started-v1.md)
- [Diagnose voice incidents with Amazon Bedrock](https://docs.operata.com/docs/guides-mcp-bedrock-agentcore.md)
- [Send your first observation](https://docs.operata.com/docs/guides-send-first-observation.md)