Introducing Astro API: Production-Ready and Generally Available

Astro API is now Generally Available

In April 2024, we introduced the Astro API Beta as a major step forward in making Astro programmable by default—giving teams the ability to automate provisioning, reduce manual operational work, and integrate Astro into CI/CD and internal tooling.Since then, adoption has grown far beyond our initial expectations. Teams are using the API to automate onboarding, monitor deployment status, and build Astro into their internal tooling and automation workflows. What started as an experimental capability has become critical infrastructure for many of our customers.

Today, we’re excited to announce that Astro API is now generally available.

What’s in Astro API?

The new Astro API delivers programmatic control over your entire Astro infrastructure, now with dedicated support and scheduled updates. All routes will work from the v1 path.

Common workflows teams are building:

• Automated onboarding for new teams and environments
• CI/CD integration for deployment and configuration management
• Multi-environment synchronization across dev, staging, and production
• Custom monitoring and alerting pipelines
• Self-service provisioning through internal portals

Moving to GA is about meeting customers where they are today. The Astro API is no longer “nice to have”; it’s powering real automation in real environments. Moving to GA enables us to provide:

Production-ready stability: A versioned API contract with clear backward compatibility guarantees and advance notice for any breaking changes.

Comprehensive documentation: Complete OpenAPI specifications, practical examples, and migration guides to help teams get started quickly.

Standard support: API usage is now covered under standard Astronomer support SLAs.

You can authenticate using Organization, Workspace, or Deployment API tokens depending on your scope and security requirements. All token types respect existing RBAC policies.

Example: Creating a Deployment

curl -X POST https://api.astronomer.io/v1/organizations/organizationId/deployments \
     -H "Authorization: Bearer <token>" \
     -H "Content-Type: application/json" \
     -d '{
  "astroRuntimeVersion": "9.1.0",
  "clusterId": "clmh9g6zj000008mg77if5wa2",
  "executor": "CELERY",
  "isCicdEnforced": true,
  "isDagDeployEnabled": true,
  "isHighAvailability": true,
  "name": "My deployment",
  "schedulerSize": "SMALL",
  "type": "DEDICATED",
  "workspaceId": "clmh8ol3x000008jo656y4285"
}'

See the API documentation for the complete reference.

Deprecation notice: Astro API Beta
Alongside this announcement, we’re officially deprecating the Astro API Beta, with end-of-support scheduled for January 2027. Customers will have 12 months to migrate from the beta API to Astro API v1. The beta API remains fully supported through the migration window. Check the migration guide for details.

Getting Started

The Astro API documentation and OpenAPI specifications are available now at www.astronomer.io/docs/astro/api.

To start building:

1. Generate an API token in the Astro UI (Organization, Workspace, or Deployment scope)
2. Review the Getting Started guide
3. Download the OpenAPI specs for your preferred tools

Whether you’re building new automation or migrating from the beta API, this is the stable foundation you need to programmatically manage Astro at scale.