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

# Introduction

> Read your Cortado leads and contacts from your own tools over HTTPS

## Overview

The Cortado API is a small, **read-only** HTTP JSON API. It lets your own tools look up leads and contacts belonging to your organization.

<Note>
  The API is in **beta** and is enabled per organization. Turn it on from **Settings > Integrations > API Keys**, or email [support@cortado.pro](mailto:support@cortado.pro) to request access. See the [API Keys guide](/guides/integrations/api-keys) for the setup walkthrough.
</Note>

## Base URL

```
https://api.cortado.pro/api/v1/ext
```

Every endpoint is served over HTTPS and returns JSON.

## Quick Start

```bash theme={null}
curl -H "Authorization: Bearer cort_your_key_here" \
  https://api.cortado.pro/api/v1/ext/leads/8f14e45f-ceea-467a-9e6a-1f2b3c4d5e6f
```

## What You Can Do

<CardGroup cols={2}>
  <Card title="Authentication" icon="key" href="/api/authentication">
    Sending your API key and what the limits are
  </Card>

  <Card title="Errors" icon="triangle-exclamation" href="/api/errors">
    Status codes and the error envelope
  </Card>

  <Card title="Get a Lead" icon="filter" href="/api/leads">
    <code>GET /leads/\{id}</code>
  </Card>

  <Card title="Get a Contact" icon="address-book" href="/api/contacts">
    <code>GET /contacts/\{id}</code>
  </Card>
</CardGroup>

## Conventions

* **Read-only.** There are no create, update, or delete endpoints. A key can never change your data.
* **Scoped to one organization.** A key reads only the organization it was created in.
* **Timestamps** are RFC 3339 in UTC — for example `2026-10-05T18:30:00Z`.
* **Optional fields are always present**, with `null` when there is no value. A field is omitted only where noted.
* **IDs are UUIDs.** You can copy a record's ID from its URL in Cortado.

## Stability

Response shapes are defined separately from Cortado's internal data model, so day-to-day product changes don't alter what your integration receives. New fields may be added over time — write your integration so unknown fields are ignored rather than treated as errors.