Hi Railway team,

I’m building an approval-gated deployment pipeline and need a supported, machine-readable way to verify the current Automatic Deployments state for a specific Railway service/environment.

Is there a supported field or query in the Railway Public GraphQL API:

https://backboard.railway.com/graphql/v2

that returns whether Automatic Deployments are currently enabled or disabled for a specific service in a specific environment whose source is connected to GitHub?

We need a read-only result with semantics equivalent to:

ENABLED

DISABLED

The check must be suitable for running immediately before:

serviceInstanceDeployV2(serviceId, environmentId, commitSha)

Our deployment pipeline is intentionally separated into independent privileged actions:

git.commit

→ approval

→ git.push

→ approval

→ railway.deploy

→ approval

Automatic Deployments are disabled because a git.push must never cause a production deployment.

Immediately before railway.deploy, the executor re-validates every security precondition, including:

“Automatic Deployments are still disabled.”

Our implementation is fail-closed:

ENABLED → ABORT

DISABLED → may proceed

UNKNOWN → ABORT

We deliberately do not treat UNKNOWN as DISABLED.

What we need from you:

1. Is there a supported Public GraphQL API field/query that exposes this state?

2. If yes, please provide the exact field/query path and confirm whether it is part of the supported/stable Public API surface.

3. Can it be queried with a project-scoped Railway token, rather than requiring an account-wide token?

4. If the state is exposed as part of a broader service configuration object, please identify the exact field.

What we have already checked:

• The Automatic Deployments documentation describes enabling/disabling it through the Railway dashboard, but does not document a public API field.
• The documented serviceInstance/service configuration fields do not appear to expose auto-deploy state.
• Railway MCP has a serviceAutoDeployTool that returns data such as:

{ "enabled": false, "canEnable": true }

That is exactly the information we need, but we do not know whether it is backed by a supported Public GraphQL field.

We do NOT want to rely on:

• dashboard scraping
• browser automation
• undocumented/private GraphQL fields
• reverse-engineering CLI output
• treating an unknown state as disabled

If there is no supported Public API field, could you also clarify:

1. Is exposing Automatic Deployments state through the Public API planned or available as a feature request?

2. Is there another supported machine-readable signal that proves a push to the connected GitHub branch cannot automatically deploy this service/environment?

3. Would disconnecting the GitHub source entirely be a supported architecture while still using:

serviceInstanceDeployV2(serviceId, environmentId, commitSha)

to deploy an exact GitHub commit SHA?

If that works, it could structurally eliminate the Automatic Deployments risk.

Reference details:

Project:

qsnera-reels-bot

Service:

axiom-checklist-bot

Environment:

production

Source:

rodion2yalanskiy-netizen/axiom-checklist-bot

Branch:

main

Automatic Deployments:

currently disabled in the Railway dashboard

Intended deployment mutation:

serviceInstanceDeployV2(serviceId, environmentId, commitSha)

No secrets or credentials are included in this request.

Thank you.