a month ago
Draft — Railway Support Request
Subject: API tokens returning "Not Authorized" on all GraphQL v2 requests
Hi Railway Support,
I'm experiencing a consistent authentication failure with account tokens against your GraphQL v2 API. Every token I generate returns "Not Authorized" on even the most basic queries, including { me { id name email } }.
Account: weberd436@gmail.com
Workspace: dave2026's projects
What I've tried:
- Generated 4 separate tokens from Account Settings → Tokens, each scoped to "dave2026's projects"
- Tested against both https://backboard.railway.app/graphql/v2 and https://backboard.railway.com/graphql/v2
- Tried both Authorization: Bearer and Railway-Token: headers
- All tokens are 36 characters (UUID format) — correct length
- Tokens were generated on mobile browser (railway.com)
Sample request:
POST https://backboard.railway.app/graphql/v2
Authorization: Bearer
Content-Type: application/json
{ "query": "{ me { id name email } }" }
Response (all tokens, all attempts):
{
"errors": [{
"message": "Not Authorized",
"extensions": { "code": "INTERNAL_SERVER_ERROR" }}]
}
Questions:
- Is there an email confirmation step required after token creation that isn't shown in the mobile UI?
- Are tokens created on mobile browser treated differently than desktop?
- Is there a known issue with the GraphQL v2 API and workspace-scoped tokens?
I need programmatic API access to manage cron schedules and monitor deployments on my project. Please advise on what's blocking authentication.
Thanks,
Dave Weber
4 Replies
a month ago
The { me { ... } } query only works with account tokens, not workspace tokens. Because you scoped each token to "dave2026's projects," they were created as workspace tokens, which cannot access personal account data. To fix this, create a new token at railway.com/account/tokens and select "No workspace" in the dropdown - that produces an account token that works with the me query and also has access to all your workspaces.
Status changed to Awaiting User Response Railway • 27 days ago
a month ago
Thank you — tried a new token with "No Workspace" selected, still getting "Not Authorized" on { me { id name email } }. All tokens generated via mobile browser (railway.com on iOS/Android) are failing. Is there a known issue with token creation on mobile? Should I try generating the token from a desktop browser instead? The token shows immediately after creation with no confirmation step.
Status changed to Awaiting Railway Response Railway • 27 days ago
a month ago
There are no known issues with mobile token creation, but mobile browsers can silently truncate tokens during copy, which would cause exactly this "Not Authorized" error. Please try generating a new account token (with "No workspace" selected) from a desktop browser at railway.com/account/tokens, and then test it in the GraphiQL playground on that same desktop - the playground handles request construction automatically, so it will confirm whether the token itself is valid.
Status changed to Awaiting User Response Railway • 27 days ago
a month ago
I successfully generated a token from my desktop pc. Thanks for your help. You can close this issue.
Status changed to Awaiting Railway Response Railway • 27 days ago
Status changed to Solved Railway • 27 days ago