For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
      • AstroFully-managed data operations, powered by Apache Airflow.
      • Astro Private CloudRun Airflow-as-a-service in your environment.
      • Professional ServicesExpert Airflow services for your enterprise's success.
    • Tools
      • Cosmos
      • Orbiter
      • CLI
      • AI SDK
      • Agents
      • Blueprint
      • UpdatesThe State of Airflow 2026See the insights from over 5,800 data practitioners in the full report. Download Now ➔
  • Customers
  • Docs
    • Insights
      • Blog
      • Webinars
      • Resource Library
      • Events
    • Education
      • Academy
      • What is Airflow?
  • Pricing
Get Started Free
  • Astro API v1
    • Overview
    • Get started
    • Versioning and support
    • Migrate to v1
    • Deploy with the API
  • API Reference
    • Changelog
    • Book Office Hours

Product

  • Platform Overview
  • Astro
  • Astro Observe
  • Astro Private Cloud
  • Security & Trust
  • Pricing

Tools & Services

  • Cosmos
  • Docs
  • Professional Services
  • Product Updates

Use Cases

  • AI Ops
  • Data Observability
  • ETL/ELT
  • ML Ops
  • Operational Analytics
  • All Use Cases

Industries

  • Financial Services
  • Gaming
  • Retail
  • Manufacturing
  • Healthcare
  • All Industries

Resources

  • Academy
  • eBooks & Guides
  • Blog
  • Webinars
  • Events
  • The Data Flowcast Podcast
  • All Resources

Airflow

  • What is Airflow
  • Airflow on Astro
  • Airflow 3.0
  • Airflow Upgrades
  • Airflow Use Cases
  • Airflow 2.x End of Life

Company

  • Our Story
  • Customers
  • Newsroom
  • Careers
  • Contact

Support

  • Knowledge Base
  • Status
  • Contact Support
GitHubYouTubeLinkedInx
  • Legal
  • Privacy
  • Terms of Service
  • Consent Preferences

  • Do Not Sell or Share My Personal information
  • Limit the Use Of My Sensitive Personal Information

Apache Airflow®, Airflow, and the Airflow logo are trademarks of the Apache Software Foundation. Copyright © Astronomer 2026. All rights reserved.

LogoLogo
On this page
  • Available versions
  • Version upgrades and breaking changes
  • Versioning approach
  • OpenAPI specification
Astro API v1

Astro API versioning, maintenance, and support

Edit this page
Built with

The Astro API is available in both Generally Available (GA) and beta versions. GA versions provide stable, production-ready contracts for long-term integrations.

Available versions

VersionStatusBase URLRelease DateEnd of Support
v1GAhttps://api.astronomer.io/v1/January 28, 2026Active
v1beta1Deprecatedhttps://api.astronomer.io/iam/v1beta1/
https://api.astronomer.io/platform/v1beta1/		April 2024January 2027

v1beta1 users have a 12-month migration window to transition to v1. See the v1 migration guide for key changes and migration steps.

Version upgrades and breaking changes

The Astro API uses a major.minor versioning strategy to provide stability while allowing for continuous improvement.

Versioning approach

Major version

The API major version is indicated in the URI path. For example, v1 APIs use the base URL:

https://api.astronomer.io/v1/

Breaking changes require a new major version with a dedicated migration guide and deprecation timeline.

Minor version

You can pin to a specific minor version using the X-API-Version header:

$curl --location 'https://api.astronomer.io/v1/organizations/<org-id>/clusters' \
>--header 'Authorization: Bearer <your-api-token>' \
>--header 'X-API-Version: 1.0'

If you don’t specify the X-API-Version header, your requests automatically use the latest minor version within the major version. This ensures you receive non-breaking improvements and new features automatically.

OpenAPI specification

You can download the v1 OpenAPI specification for the Astro API from:

  • Latest minor version: https://api.astronomer.io/spec/v1
  • Specific version: https://api.astronomer.io/spec/v1.0

The /spec/v1 endpoint always returns the latest minor version within the v1 major release, while specific version endpoints like /spec/v1.0 return that exact specification.