# Introduction

What the LeadUp API does, where to send requests and what to read first.

The LeadUp API lets your code read and write the same pipeline your team works in the app: the companies you prospect, where each one stands, and when you follow up next. Everything it returns belongs to one organization, the one your key was created in.

## Base URL

Every request goes to one host, with the version in the path:

```text title="Base URL"
https://api.leadup.group/v1
```

Requests and responses are JSON, sent over HTTPS. Dates are ISO 8601 in UTC, and ids are UUIDs.

## What you can reach

The public API covers **leads**: list them, read one, create one, update one (move its stage or schedule the next follow-up) and delete one. More resources join it as they become public; the [changelog](/changelog) records each one.

<Note title="One organization per key">
  A key never reaches another organization's data. To work with two organizations, create a key in each.
</Note>

## Read next

<Cards>
  <Card href="/guides/first-request" title="Your first request">Create a key, send it, and read a page of leads.</Card>
  <Card href="/guides/authentication" title="Authentication">Organization keys and personal tokens, and when to use each.</Card>
  <Card href="/reference" title="API reference">Every endpoint, with its parameters and responses.</Card>
  <Card href="/mcp" title="MCP server">Let an AI agent work your pipeline.</Card>
</Cards>