a month ago
Railway Account Token API authentication is failing.
I have an active Hobby workspace and created a true Account Token from Account Settings → Tokens with “No workspace”.
The token is passed as Authorization: Bearer exactly as documented.
Even the official test query query { me { name email } } returns Not Authorized with INTERNAL_SERVER_ERROR.
This also fails from GitHub Actions.
My project token works for project-scoped read/deployment operations, but Account Token authentication fails before any project or scale mutation is attempted.
Latest traceId: 4944166118978912635
Please check whether Public API authentication is disabled or broken for my Railway account/workspace.
Pinned Solution
a month ago
I just created an account token, and tested it with this curl example from the docs (the query query { me { name email } } test you mentioned), and it worked. Maybe try to delete that token, and generate a new one, and test it. Also, make sure the token in the Authorization header isn't wrapped by <>, so the correct approach would be like this: Authorization: Bearer b2fad446-e2a9-4501-8v77-1ah8a5ye10df.
2 Replies
a month ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 1 month ago
a month ago
I just created an account token, and tested it with this curl example from the docs (the query query { me { name email } } test you mentioned), and it worked. Maybe try to delete that token, and generate a new one, and test it. Also, make sure the token in the Authorization header isn't wrapped by <>, so the correct approach would be like this: Authorization: Bearer b2fad446-e2a9-4501-8v77-1ah8a5ye10df.
a month ago
Thanks! I created a brand-new Account Token with “No workspace” and replaced the GitHub Actions secret.
This time the authentication worked successfully:
query { me { ... } } passed
Project access worked
railway link succeeded
railway scale succeeded
I also tested autoscaling end-to-end:
3 → 4 replicas: successful
4 → 3 replicas: successful
Worker capacity changed from 6 → 8 → 6 slots correctly
So it looks like the previous Account Token itself was the problem. Thanks for the suggestion!
Status changed to Open medim • about 1 month ago
Status changed to Solved medim • about 1 month ago