Hey there! We've found the following might help you get unblocked faster:

• 🧵 API - Creating deployment triggers

• 🧵 API Token "Not Authorized" Error for Public API and MCP Automation

• 🧵 Fails on Dify API deployment

• 🧵 use railway api to create service in project?

If you find the answer from one of these, please let us know by solving the thread!

Subject: Pro Account - API Token Generation Issue

I have a Railway Pro subscription but cannot generate personal API tokens

because my account was created via GitHub OAuth. I need personal tokens

(starting with "token_") for deployment automation.

Current situation:

- Pro subscription active

- Account created via GitHub OAuth

- Can only generate project tokens (UUIDs)

- Need personal tokens for API deployments

Please enable personal token generation for my account.

The correct API endpoint is https://backboard.railway.com/graphql/v2
Whereas you are using: https://backboard.railway.app/graphql/v2

Try this! Do let me know, if that works for you

Any update, jonejacobsen

@clashing
thanks for the suggestion - and the correct endpoint.

However, the endpoint change alone doesn't resolve the authorization issue. The core problem is with the token type and its permissions:

## This is where I am at:

1. You were right about the endpoint :

- https://backboard.railway.com/graphql/v2 - Correct

- https://backboard.railway.app/graphql/v2 - Returns "Not Authorized"

2. The real issue is token permissions

- Project tokens (UUID format) are READ-ONLY

- They cannot perform mutations like serviceInstanceRedeploy or variableCollectionUpsert

- This is why we're getting "Not Authorized" even with the correct endpoint

3. Testing results:

```javascript

// with project token + correct endpoint

// still fails for mutations

{

"errors": [{

"message": "Not Authorized"

}]

}

```

4. Probable solution:

- Need a Personal Access Token (starts with token_)?

- Project tokens simply don't have deployment permissions

- This limitation isn't clearly documented

So while your endpoint correction was , the authorization issue persists due to Railway's token permission model. For deployment automation, we need personal/team tokens, not project tokens.

Thanks for pointing us in the right direction with the endpoint though.

For clarity - this it not solved, even if brody changed the status

Oh, so you got the correct endpoint, but even now the token is posing issues. Let me see if I can help

Thanks! I am unable to generate a token with the right scope. Looking at the documentation (https://docs.railway.com/guides/public-api) I do not have an option to create a team token ( I am on a Pro plan), and the personal token I should be able to create seems to have the rights of a project token, since I consistently get "Not Authorized".

Can you confirm whether this is returning a response for you, or not?

By the way, while generating an account token, are you sure you selected NO TEAM from the dropdown?

And by the way, it's mentioned in the docs that Project Tokens can only be used to authenticate requests that just give information about your account (name, & email). So, for all mutations query, one has to use the ACCOUNT TOKEN (via the Team Token section)

I can create a token both from my account settings and from the project settings (project token). For the personal tokens, I have tried selecting and not selecting a project. I am unable to create a team token (the option is not offered to me). All combinations available returns the same error. I suspect a config issue since I cannot create a team token, and have considered it using OAuth (Github) might be involved. Any experience with this?

https://railway.com/account/tokens is the page from where you could create the Personal Token (made via the Team Token section, with no team selected).

And every token in Railway follows the uuid pattern, irrespective of its nature.

So, I guess the issue is something else. As a last resort, could you share screenshot of the request that you are making. Can you try the graphQl playground that Railway provides in their doc?

I understand, this is the error. We have been incorrectly assuming that UUID tokens are Project tokens and used Project-Access-Token: , not Authorization: Bearer <my-personal-token>. Thanks for helping me resolve this!