Skip to main content
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. Check the lifecycle recap for the up-to-date status of each endpoint.

​
Core Qualities

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

Unified

The Lucca API is unified, meaning it normalizes the dozens of APIs of all the Lucca applications into one coherent data model.

Documented

The Lucca API is documented here, with general articles about the main features of the API; guides that describe how to achieve common integration scenarios; and the API reference.

Long-Term Support

In order to give you peace of mind, the Lucca API abides to a strict versioning strategy in order to avoid breaking existing integrations.

Irresistible

In reference to Kirsten L. Hunter’s book, 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.

​
Core Features

Standard OAuth 2.0 Authentication

Your data is safely secured.

REST API (JSON)

Create, update and delete objects from the Lucca data model.

Webhooks

React to changes as soon as they occur.

Versioning

No more unexpected breaking changes.

​
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, 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.