Railway
Org-level connection
Railway is connected once at the org level by an admin. The credential is shared across all groups that have been granted access — individual team members don't need to connect their own accounts.
Getting your API key
Go to railway.app and sign in
Click your avatar (top-right) → Account Settings → Tokens
Click "New Token", give it a name (e.g. "On Belay"), and copy the token
Paste it below
Ready to connect?
Go directly to the integrations page in your dashboard.
Permissions (scopes)
These are the data scopes On Belay can be granted for Railway. Your org admin controls which scopes are enabled per group.
| Scope | Description | Access |
|---|---|---|
project:read | Read projects, services, and deployments | Read only |
project:write | Trigger deployments and manage services | Read / Write |
environment:read | Read environment variables | Read only |
Troubleshooting
"Invalid API key" or "Unauthorized" error
Double-check that you copied the full key without any leading/trailing spaces. Some platforms show a truncated preview — make sure to copy the full token. If the key was generated with restricted scopes, verify it includes the permissions listed above.
Connected but Claude can't access data
Check that your group has been granted access to this integration in On Belay → Groups → [your group] → Integrations. Also verify the specific scopes your group is permitted to use match what your query requires.
The key expires or stops working
Some API keys have expiration policies. Generate a new key in Railway and update it in On Belay → Integrations → Railway → Update key. Consider creating a dedicated service account or machine user for On Belay so the key isn't tied to a personal account.
Still stuck? We're happy to help.
Contact support →