Skip to content
Project token "No Authorized"
cordoce
OP

a month ago

As of October 6, 2026, any new Environment/Project Token in the tender-blessing project (in any environment) returns 'Not Authorized' (CLI whoami/variables, and GraphQL /directographerql/v2 with Authorization: Bearer). Older tokens managed prior to that date continue to work normally. Tested on 2 machines and 2 CLI versions (5.62.1 and 5.63.4); network propagation and origin issues have been ruled out. Could there be an issue with the token issuance/validation service for this account?

Solved

1 Reply

Railway
BOT

a month ago

Project tokens are not sent as Authorization: Bearer. They use the Project-Access-Token header, and a project token is always refused by me-style queries such as railway whoami, because it authenticates as the project rather than as a user, so a "Not Authorized" there is expected even for a valid, brand-new token.

To confirm a new token is live, send query { projectToken { projectId environmentId } } to https://backboard.railway.com/graphql/v2 with the Project-Access-Token: <TOKEN> header. It returns the project and environment the token is bound to.

For the CLI, a project token is supplied through the RAILWAY_TOKEN environment variable, and commands scoped to that project and environment (like railway variables) are the ones it can run.


Status changed to Awaiting User Response Railway • about 1 month ago


Railway
BOT

a month ago

This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!

Status changed to Solved Railway • about 1 month ago


Welcome!

Sign in to your Railway account to join the conversation.

Loading...