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

# The Lucca API

> The Lucca API is the unified, documented, long-term supported and irresistible API for all of Lucca's enterprise applications.

<Warning>
  Some Lucca API endpoints are still in **beta** and may not be feature-complete. They are marked with a "BETA" badge in the API Reference.

  **Like all previous legacy API endpoints, beta endpoints are susceptible to breaking changes.**

  Once out of beta, endpoints are considered **stable** and subject to our [deprecation policy](/documentation/using-api/versioning#deprecation-policy).
  Check the [lifecycle recap](/api-reference/latest/lifecycle) for the up-to-date status of each endpoint.
</Warning>

## Core Qualities

The Lucca API was built to reach 4 core qualities in order to help you build awesome integrations.

<CardGroup cols={2}>
  <Card title="Unified" icon="merge" iconType="light">
    The Lucca API is **unified**, meaning it normalizes the dozens of APIs of all the Lucca applications into
    one coherent data model.
  </Card>

  <Card title="Documented" icon="book-open-cover" iconType="light">
    The Lucca API is documented here, with general articles about the main features of the API;
    [guides](../../guides) that describe how to achieve common integration scenarios; and the [API reference](../../api-reference/latest).
  </Card>

  <Card title="Long-Term Support" icon="block-brick" iconType="light">
    In order to give you peace of mind, the Lucca API abides to a [strict versioning strategy](../using-api/versioning)
    in order to avoid breaking existing integrations.
  </Card>

  <Card title="Irresistible" icon="heart" iconType="light">
    In reference to [Kirsten L. Hunter's book](https://www.manning.com/books/irresistible-apis),
    our goal is to make the Lucca API irresistible. As a result, the Lucca API should **delight the developers
    (that's you) who use them**.
  </Card>
</CardGroup>

***

## Core Features

<CardGroup cols={2}>
  <Card title="Standard OAuth 2.0 Authentication" icon="key" iconType="light" href="../using-api/authentication">
    Your data is safely secured.
  </Card>

  <Card title="REST API (JSON)" icon="brackets-curly" iconType="light" href="../../api-reference">
    Create, update and delete objects from the Lucca data model.
  </Card>

  <Card title="Webhooks" icon="webhook" iconType="light" href="../webhooks">
    React to changes as soon as they occur.
  </Card>

  <Card title="Versioning" icon="code-branch" iconType="light" href="../using-api/versioning">
    No more unexpected breaking changes.
  </Card>
</CardGroup>

***

## About the Legacy API

The Lucca API will progressively gain in scope, in particular regarding resources. As long as it is not complete,
the [Legacy APIs](../../api-reference/legacy), which are its primitive version, remains documented alongside.

The Legacy APIs are to be considered deprecated but with no definitive sunset date. Once a resource is added in
the Lucca API, the corresponding endpoint in the Legacy APIs will remain operational for at least 6 months.
Which makes it possible for you to migrate to the Lucca API.