N/A

adding webhooks works just fine, you might be trying to use the wrong api key

hey @Brody , I'm created a team and created another project within it and would like to add webhook to it.

All other queries like create project, redploy or template deploy are working with my api but not the webhook, any idea what's getting wrong?

Also, I need to create the API token in my personal account right? I was not able to create any api token in my team workspace

It is working in personal projects but not in team

you need to create the API token for the team account

can I know, the URL for it

I can't find it

select your hobby account and then select the team when creating a token

when, doing it, I'm getting auth errors

what is your status on the team

you may have to ask the owner to create the API token for you

I'm the admin

please show me the errors

sure

This is the request:

mutation createWebhook {
  railway {
    webhookCreate(input: {projectId: "19f097bd-c834-48f1-b55e-50123c01f982", url: "https://webhook.site/ba79d712-b3b4-4221-a5d5-3acf9ff296f7"}) {
      id
      lastStatus
      projectId
      url
    }
  }
}

This is the response

{
  "data": null,
  "errors": [
    {
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR"
      },
      "locations": [
        {
          "column": 26,
          "line": 1
        }
      ],
      "message": "Not Authorized",
      "path": [
        "webhookCreate"
      ]
    }
  ]
}

Just created a new empty project, and new API token and tested it out

Even tried creating a project token and used it for creating webhook, but facing the same issue

try using a "No Team" token

Same, error

i was able to replicate this issue using a team token, if i use a "no team" token i am able to add webhooks to pro projects that im a part of

Let me create a new token and project and then check with it.

Nice, I was able to replicate it and create webhook. But don't you think it is not the desired way?

if it works it works 🙂

Seems like the personal tokens are throwing errors now, but a new error message:

{
    "errors": [
        {
            "message": "Nice try. Psst, we have a bug bounty! See the Discord",
            "locations": [
                {
                    "line": 2,
                    "column": 5
                }
            ],
            "path": [
                "webhookCreate"
            ],
            "extensions": {
                "code": "INTERNAL_SERVER_ERROR"
            }
        }
    ],
    "data": null
}

have you tried using the team token?

yes, no use

can you add a webhook via the dashboard?

yes

if you can add a webhook via the dashboard you can do so via the API as well

But, using the public API, I was not able to create webhook using both the teams API token or the Personal Token.

Am I missing something here, based on our previous conversation, I was able to create webhooks using personal token, but now I was not able to create using them.

Error with team token:

{
  "data": null,
  "errors": [
    {
      "extensions": {
        "code": "INTERNAL_SERVER_ERROR"
      },
      "locations": [
        {
          "column": 26,
          "line": 1
        }
      ],
      "message": "Not Authorized",
      "path": [
        "webhookCreate"
      ]
    }
  ]
}

The error with personal token.

{
    "errors": [
        {
            "message": "Nice try. Psst, we have a bug bounty! See the Discord",
            "locations": [
                {
                    "line": 2,
                    "column": 5
                }
            ],
            "path": [
                "webhookCreate"
            ],
            "extensions": {
                "code": "INTERNAL_SERVER_ERROR"
            }
        }
    ],
    "data": null
}

no issues, I guess using url to be localhost is getting me the error.

In order to create webhook with Public API.

1. use personal token (even though the project is in a team)

2. the URL, cannot he [http://localhost:3000](http://localhost:3000)

may I ask why you thought localhost would work?

No our developers used it, for testing purpose via a env variable.

okay