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

# Introduction

The Inflection Developer API gives you programmatic access to the core objects of your workspace. It's organized around these resources:

* **Contacts**: look people up by id or email, create them, and keep their attributes in sync.
* **Contact activity**: a contact's product events, marketing engagement, a change log of record properties, and the mapped Salesforce record.
* **Lists & members**: list your static and dynamic lists, and manage static lists and the contacts on them.
* **Emails**: create HTML emails in Inflection, list emails, and fetch emails (both HTML and visual editor) by ID.
* **Journeys**: list journeys and read a journey's schedule and derived status.
* **Stats**: send and engagement metrics for journeys and emails, with rollups across many journeys or emails in one call.
* **Product users**: the product logins underneath a contact, by id or email, with async create and update.
* **Organizations**: company accounts, their product users, and a contact's memberships.
* **Email versions**: push per-contact versions of a [Personalized Email Asset](/agents/personalized-email) via `POST /v1/email-versions` for 1:1 sends at scale. See [Send Personalized Emails from Clay](/agents/send-personalized-emails-from-clay) for a worked example.

<Info>
  Every path lives under `/v2` on the API gateway: `https://api.inflection.io`. `/v2` is `/v1` plus more: every `/v1` endpoint is served under `/v2` unchanged, and `/v1` remains published, so existing clients keep working. Journeys, stats, the email and list collections, product users, and organizations are `/v2` only. The one exception is `POST /v1/email-versions`, which is served under `/v1`.
</Info>

The API is JSON over HTTPS, authenticated with a bearer token, either a Personal Access Token or an OAuth access token (see [Authentication](/api-reference/authentication)). Reads are synchronous; contact writes are processed asynchronously and return a transaction you poll (see [Asynchronous writes](/api-reference/async-writes)).

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/api-reference/quickstart">
    From zero to your first response in two calls.
  </Card>

  <Card title="Authentication" icon="key" href="/api-reference/authentication">
    Tokens, scopes, and what 401 vs 403 mean.
  </Card>
</CardGroup>


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.