Atlan API

Atlan is a modern data workspace that makes collaboration among diverse users (like managers, analysts and engineers) easier, increasing efficiency and agility in data projects ✨

Atlan is built on an OpenAPI architecture, hence everything that is visible on the product is powered by APIs. We are gradually opening up more APIs for our users. If you are looking for an API that you don't see here, please reach out to us.

This is the documentation for version 2.0.0 of the API. Last update on Dec 21, 2022.

Base URL


We are also experimenting with a new Developer Portal — exploring common use cases in more detail and showing how to use our SDKs (currently under development). We'd love your thoughts on how you use (or avoid) one site or the other, or even use them in combination. Just give your Atlan contact a shout with any feedback!

Important notes

Important notes

This site only contains documentation about the APIs, and is not built from the APIs themselves.

All changes noted in the API Changelog are changes to this documentation, and not to the underlying APIs of Atlan.

For clarity:

  • We may occasionally make mistakes in the documentation 🙈
  • When we discover these, we go back to correct them as quickly as we can 🧑‍💻
  • The site may show these as breaking changes in the API 🚨, but in reality we're only fixing broken documentation 📚
  • (Without fixing documentation where it's wrong, what you see in the documentation wouldn't actually work)
  • For the avoidance of doubt: the APIs themselves are not changing 😅

How we've organized the documentation

In most cases, our API does not have separate endpoints for different types of assets. For example, we do not have different endpoints for data sources and business intelligence objects.

Instead, we have many endpoints that you can use to manage many different types of assets.

So we have organized the documentation into two general areas:

  • The tags you see along the left provide succinct examples of common operations. These use case examples provide the minimal set of information required to be complete.
  • The very last Canonical tag provides the full documentation of API endpoints that are used for many different use cases. Here you can find the extensive list of options that you can apply, if you want to extend beyond the common use cases.

You can also distinguish between these two approaches by looking at the URL of each endpoint:

  • The use case examples will all end with a #operationId. You can actually drop this from the URL, as it is not needed by the API. It is only needed by the formal specification we use to document the operations, to keep each one unique.
  • The canonical endpoints will have no #operationId at the end of their URL.


Atlan APIs use certain common terms and properties that are based on our product fundamentals. To help you get oriented, here are the common concepts in our API documentation. (For a deeper dive into product terminology, head over to our Product Documentation)

Key concepts

  • Asset — all objects that provide context to your data, such as tables, columns, databases, BI dashboards and so on.
  • Process — the transformations that link together upstream and downstream assets in lineage.
  • Unique identifiers — control how Atlan creates vs updates assets.
  • Type definitions — control what metadata is used to describe each different kind of asset (for example a Table vs a Column).


Send all requests to Atlan's APIs using a bearer token in the Authorization header.

For details on creating a bearer token, see our API authentication article.


Each update we make to the documentation automatically builds an updated Postman collection at: — you can use this quickly get started with the APIs.

See our Getting started with the APIs article for more details.