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

# API & Developer

> Generate API keys and access EolasFlow programmatically

The Developer section provides programmatic access to EolasFlow. Generate API keys to integrate with your own applications, automate workflows, or build custom dashboards.

## API Keys

Navigate to **API** in the Organization section.

### Generate an API Key

<Steps>
  <Step title="Go to API">
    Navigate to **API** in the Organization section.
  </Step>

  <Step title="Create Key">
    Click **Generate API Key** and give it a descriptive name (e.g., "CRM Integration", "Reporting Dashboard").
  </Step>

  <Step title="Copy Key">
    Copy the API key immediately — it won't be shown again.
  </Step>
</Steps>

<Warning>
  Store your API key securely. Do not expose it in client-side code or public repositories.
</Warning>

### Manage Keys

View all active API keys, their creation dates, and last usage. Revoke keys that are no longer needed.

## Authentication

All API requests require the API key in the Authorization header:

```bash theme={null}
curl -H "Authorization: Bearer your-api-key" \
  https://api.eolasflow.ai/api/v1/agents/
```

## Available Endpoints

The EolasFlow API provides access to:

| Resource          | Operations                           |
| ----------------- | ------------------------------------ |
| **Assistants**    | List, create, update, delete         |
| **VoiceFlows**    | List, create, update, toggle status  |
| **Contacts**      | List, create, update, delete, import |
| **Conversations** | List, get details, export            |
| **Phone Lines**   | List, purchase, release              |
| **Knowledge**     | List collections, upload documents   |
| **Tasks**         | List, update status                  |

## Best Practices

<Tip>
  **Use Separate Keys:** Create distinct API keys for different integrations so you can revoke them independently.
</Tip>

<Tip>
  **Monitor Usage:** Check the last-used timestamp to identify stale keys.
</Tip>

## Next Steps

<CardGroup cols={2}>
  <Card title="Webhooks" icon="link" href="/guides/webhooks">
    Receive real-time call events
  </Card>

  <Card title="MCP Integration" icon="plug" href="/guides/mcp">
    Give assistants access to your tools
  </Card>
</CardGroup>