Railway Python API Docs | dltHub
Build a Railway-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Railway is a platform that provides a GraphQL API for managing cloud infrastructure, services, and deployments. The REST API base URL is https://backboard.railway.com/graphql/v2 and Requests require either a Bearer token or a Project-Access-Token header depending on the token type used..
dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv add "dlt[hub]" and start loading Railway data in under 10 minutes.
What data can I load from Railway?
Here are some of the endpoints you can load from Railway:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| projects | POST /graphql/v2 | POST | projects | List all projects |
| services | POST /graphql/v2 | POST | project.services | List all services for a project |
| environments | POST /graphql/v2 | POST | project.environments | List all environments for a project |
| deployments | POST /graphql/v2 | POST | deployments | List all deployments for a project |
| volumes | POST /graphql/v2 | POST | project.volumes | List all volumes for a project |
How do I authenticate with the Railway API?
Authentication uses either an 'Authorization: Bearer ' header for account or workspace tokens, or a 'Project-Access-Token: ' header for project-scoped tokens.
1. Get your credentials
To obtain credentials for the Railway API, navigate to your account settings by visiting https://railway.com/account/tokens. From there, you can generate either a personal account token (for broad, account-wide access) or a project-scoped token (for limited access to a specific project). Once generated, copy the token to use it in your API requests. For CI/CD or non-interactive environments, export the token as an environment variable named 'RAILWAY_API_TOKEN' (for account-scoped tokens) or 'RAILWAY_TOKEN' (for project-scoped tokens).
2. Add them to .dlt/secrets.toml
[sources.railway_source] railway_api_token = "your_railway_token_here"
dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.
How do I set up and run the pipeline?
Set up a virtual environment and install dlt:
uv init uv add "dlt[hub]"
1. Install the dlt AI harness:
uv run dlthub ai init --agent <your-agent> # <agent>: claude | cursor | codex
This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →
2. Install the rest-api-pipeline toolkit:
uv run dlthub ai toolkit install rest-api-pipeline
This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →
3. Start LLM-assisted coding:
Use /find-source to load data from the Railway API into DuckDB.
The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.
4. Run the pipeline:
uv run python railway_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline railway_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset railway_data The duckdb destination used duckdb:/railway.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
uv run dlthub show
This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.
Python pipeline example
This example loads The Railway platform utilizes a GraphQL API (not a REST API) with two primary endpoints: the primary query/mutation endpoint https://backboard.railway.com/graphql/v2 and the WebSocket endpoint for subscriptions/logs wss://backboard.railway.com/graphql/v2. from the Railway API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def railway_source(api_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://backboard.railway.com/graphql/v2", "auth": {"type": "bearer", "token": api_token}, }, "resources": [ {"name": "projects", "endpoint": {"path": "graphql/v2", "data_selector": "edges.node"}}, {"name": "deployments", "endpoint": {"path": "graphql/v2", "data_selector": "edges.node"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="railway_pipeline", destination="duckdb", dataset_name="railway_data", ) load_info = pipeline.run(railway_source()) print(load_info)
To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.
How do I query the loaded data?
Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.
Python (pandas DataFrame):
import dlt data = dlt.pipeline("railway_pipeline").dataset() sessions_df = data.projects.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM railway_data.projects LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("railway_pipeline").dataset() data.projects.df().head()
See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.
What destinations can I load Railway data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Next steps
Continue your data engineering journey with the other toolkits of the dltHub AI harness:
data-exploration— Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.dlthub-platform— Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform
Was this page helpful?
Community Hub
Need more dlt context for Railway?
Request dlt skills, commands, AGENT.md files, and AI-native context.