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

# API overview

> Drive CodeCobra from your own systems — create tasks, read deliverables, export usage.

Everything you can do in CodeCobra, you can do over HTTP. The API is the same surface the product itself uses, so there is nothing held back for the interface.

## What people build with it

* **Open a task from your tracker.** A ticket gets a label, a task opens with the description already in it.
* **Pull deliverables into somewhere else.** Have the spreadsheet CodeCobra produced land in your data warehouse or your finance folder.
* **Export usage for internal chargeback.** Split spend by team or project in your own reporting.
* **Watch a build.** Stream a task's replies into your own dashboard or chat tool.

## Getting started

<Steps>
  <Step title="Create an API key">
    **Settings → API keys → Create key.** Copy it immediately — it is shown once and never again.
  </Step>

  <Step title="Send it as a bearer token">
    ```bash theme={null}
    curl -H "Authorization: Bearer cc_your_key_here" \
      https://codecobra.ai/api/users/me
    ```
  </Step>

  <Step title="Browse the reference">
    Every endpoint is listed with its parameters and responses, grouped by what it does.
  </Step>
</Steps>

## Base URL

```
https://codecobra.ai
```

## What the API can't do

Some things are deliberately out of reach of an API key, because a key should not be able to widen its own access or start something only a browser can finish:

* Signing in, resetting a password, or setting up two-factor
* Creating, listing or revoking API keys — a leaked key cannot mint another
* Linking or unlinking a Google or GitHub identity
* Connecting or disconnecting GitHub, since reconnecting needs a browser redirect. Reading installations, repositories and branches works normally.

<Card title="Authentication" icon="key" href="/api/authentication">
  Creating keys, using them, and what they can reach.
</Card>