Skip to main content
Version: 0.30

Houston API

The Astronomer Houston API is the source of truth across the entire Astronomer platform.

For Astronomer Software users, our API is an easy way to do any of the following:

  • Query the platform's database for information about a user, Workspace, or Deployment
  • Perform CRUD operations on entities scoped to the Astronomer platform, including Airflow Deployments, Workspaces, and users

For example, you can:

  • Delete a deployment
  • Look up a deployment's resource config
  • Add a user to a Workspace
  • Make a user a System Administrator

Anything you can do with the Software UI, you can do programmatically with the Astronomer Houston API.


If you're using the Astronomer Houston API and you're migrating from Astronomer Certified (AC) to Astro Runtime, you'll need to replace airflowVersion arguments with runtimeVersion arguments in your scripts. For more information about migrating a Deployment from Astronomer Certified to Astro Runtime, see Migrate a Deployment from Astronomer Certified to Astro Runtime.

Getting started

The Astronomer Houston API is available in a GraphQL Playground, "a graphical, interactive, in-browser GraphQL IDE, created by Prisma and based on GraphiQL." GraphQL itself is an open source query language for APIs that makes for an easy and simple way to manage data.

In short, the Playground is a portal that allows you to write GraphQL queries directly against the API within your browser.

For more information about the Playground features applicable to the wider GraphQL community, see GraphQL Playground's Github.

Access the GraphQL playground

The URL at which you can reach Houston's GraphQL playground depends on the platform you're running. For your installation of Astronomer, it will be https://houston.BASEDOMAIN/v1/.

For example, if you're a Software customer and your basedomain is Astronomer, you would navigate to https://houston.astronomer/v1/.


To query the Astronomer Houston API, you must first authenticate as an Astronomer user.

  1. Go to https://app.BASEDOMAIN/token and copy the API token. Alternatively, note the API Key of a service account.
  2. Open Astronomer's Houston API GraphQL Playground at https://houston.BASEDOMAIN/v1.
  3. Expand the HTTP Headers section on the bottom left of the page.
  4. Paste the API token you acquired from Step 1 in the following format: {"authorization": "<api-token>"}


Note: As you work with our API, you'll be restricted to actions allowed by both your existing role within the platform (e.g. SysAdmin or not) and your permissions within any particular Workspace (e.g. Viewer, Editor, Admin).

Query types

On Astronomer, you can ask for GraphQL:

Houston API schema

Once authenticated, you should be able to query all endpoints your user has access to. The Schema tab fixed on the right-hand side of the page is a great reference for queries and mutations we support and how each of them is structured.


Sample queries

Read below for commonly used queries. For those not in this doc, reference the "Schema" on the right-hand side as referenced above.

Query an Airflow Deployment

The workspaceDeployments query requires the following inputs:

  • workspaceUuid
  • releaseName

and can return any of the fields under Type Details:

  • config
  • uuid
  • status
  • createdAt
  • updatedAt
  • roleBindings
  • etc.

For instance, you can run the following:

query workspaceDeployments {
releaseName: "mathematical-probe-2087"
workspaceUuid: "ck35y9uf44y8l0a19cmwd1x8x"
workspace {users {emails {address, createdAt} }}

To view results, press the "Play" button in middle of the page and see them render on the right side of the page.


Query a user

To query for information about a user on the platform (e.g. "When was this user created?" "Does this user exist?" "What roles do they have on any Workspace?"), run a variation of the following:

query User {
users(user: { email: "<>"} )
roleBindings {role}

In the output, you should see:

  • The user's id
  • A list of existing roles across the cluster (e.g. Workspace Admin)
  • The status of the user (active, pending)
  • A timestamp that reflects when the user was created

Sample mutations

Mutations make a change to your platform's underlying database. For some common examples, read below.

Create a Deployment

To create a Deployment, you'll need:

  1. Workspace Admin permissions
  2. Your Workspace ID

Then, to create a Deployment, run the following:

mutation CreateDeployment {
workspaceUuid: "<workspace-id>",
type: "airflow",
label: "<deployment-name>",
config: {executor:"<airflow-executor>"},


Here, <airflow-executor> can be LocalExecutor, CeleryExecutor, or KubernetesExecutor.

Delete a Deployment

To delete a Deployment, you'll need:

  1. Permission (SysAdmin or Workspace Admin)
  2. A Deployment ID

Note: For more information about the SysAdmin role, reference our "User Management" doc.

If you don't have a Deployment ID, run astro deployment list in the Astro CLI or follow the steps in "Query an Airflow Deployment".

Then, to delete a Deployment, run the following:

mutation DeleteDeployment {
deleteDeployment (
deploymentUuid: "<deployment-id>"
) {

Create a Deployment user

To create a Deployment user, you'll need:

  1. Workspace Admin privileges
  2. A Deployment ID

If you don't have a Deployment ID, run astro deployment list in the Astro CLI or follow the steps in "Query an Airflow Deployment".

First, add the following to your GraphQL playground:

mutation AddDeploymentUser(
$userId: Id
$email: String!
$deploymentId: Id!
$role: Role!
) {
userId: $userId
email: $email
deploymentId: $deploymentId
role: $role
) {
user {
deployment {

Then, in the Query Variables tab, add the following:

"role": "<user-role>",
"deploymentId": "<deploymentId>",
"email": "<email-address>"


After you specify these variables, run the mutation.

Delete a user

To delete a user, you'll need:

  1. SysAdmin permissions
  2. userUuid

With a userUuid, run the following:

mutation removeUser {
removeUser (
userUuid: "<USERUUID>"
) {
emails {address}

Verify user email

If a user on the platform has trouble verifying their email address upon signup, you can use the Playground to manually verify it.

To run this mutation, you'll need:

  1. SysAdmin Permissions
  2. User's email address

With the email address in question, run the following:

mutation verifyEmail {
verifyEmail (
email: "<USERUUID>"

Note: To run this mutation, ensure that the user in question has already begun creating an account on the platform (i.e. the user has signed up and the platform has generated an "invite token" for that user).

Bypass user email verification

If you don't need certain users to verify their email before joining a Workspace, you can configure a bypass when adding them to a Workspace. This can be useful for minimizing friction when programmatically inviting many users to your platform.

To run this mutation, you'll need:

  • Workspace Admin permissions
  • A Workspace ID
  • The user's email address
  • The user's Workspace role
mutation workspaceAddUser(
$workspaceUuid: Uuid = "<your-workspace-uuid>"
$email: String! = "<user-email-address>"
$role: Role! = <user-workspace-role>
$bypassInvite: Boolean! = true
) {
workspaceUuid: $workspaceUuid
email: $email
role: $role
deploymentRoles: $deploymentRoles
bypassInvite: $bypassInvite
) {

Add a System Admin (Software only)

System Admins can be added either via the Software UI ('System Admin' > 'User' > 'User Details') or via an API call to Houston. To run the mutation in the GraphQL Playground, you'll need:

  • userUuid
  • role (SYSTEM_ADMIN)

Note: Keep in mind that only existing System Admins can grant the SysAdmin role to another user and that the user in question must already have a verified email address and already exist in the system.

With the uuid you pulled above, call the createSystemRoleBinding mutation by running:

mutation AddAdmin {
userId: "<uuid>"
) {

If you're assigning a user a different System-Level Role, replace SYSTEM_ADMIN with either SYSTEM_VIEWER or SYSTEM_EDITOR in the mutation above.

Create a service account

You can create Deployment and Workspace-level accounts in the Software UI as described in Deploy to Astronomer via CI/CD. Alternatively, you can create platform-level service accounts programatically via the Houston API. To create a service account via the Houston API, run the following in your GraphQL Playground:

mutation CreateSystemServiceAccount {
createSystemServiceAccount(label: "<label>", role: SYSTEM_ADMIN) {

Update environment variables

To programmatically update environment variables, you'll need:

  1. A Deployment ID
  2. A Deployment release name

If you don't have a Deployment ID, run astro deployment list in the Astro CLI or follow the steps in "Query an Airflow Deployment".

Then, in your GraphQL Playground, run the following:

mutation UpdateDeploymentVariables {
deploymentUuid: "<deployment-id>",
releaseName: "<deployment-release-name>",
environmentVariables: [
{key: "<environment-variable-1>",
value: "<environment-variable-value-1>",
isSecret: <true-or-false>},
{key: "<environment-variable-2>",
value: "<environment-variable-value-2>",
isSecret: <true-or-false>}
) {

Custom types

Any object in the Schema that maps to a custom GraphQL Type often requires additional subfields to be added to the query or mutation return object.

Below, we describe this concept in the context of a sample mutation.

Add a user to a Workspace

For example, take the "Add a user to a Workspace" mutation.

As input, you need:

  1. A Workspace ID
  2. Email address of the user
  3. The designated role for the user (for example,. Workspace "Admin", "Editor" or "Viewer")

If you don't already have a Workspace ID, run astro workspace list in the Astro CLI.

With that information, run the following:

mutation WorkspaceAddUser {
workspaceAddUser (
workspaceUuid: "<workspace-id>"
email: "<>"
) {
users {emails {address} }

In the above example, you should see the following return:

  1. The email addresses of all users in the Workspace
  2. The Workspace label
  3. The date on which the Workspace was created

Unlike the label and createdAt fields, notice that the users type field requires you to specify additional subfields, i.e. emails and then addresses.

To know which fields you can or must specify, reference the "Schema" on the righthand side of the page. As is the case here, custom types are often composed of other custom types.

Custom Type

Was this page helpful?

Sign up for Developer Updates

Get a summary of new Astro features once a month.

You can unsubscribe at any time.
By proceeding you agree to our Privacy Policy, our Website Terms and to receive emails from Astronomer.