Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Integrations: generic API incoming webhook uses APIv2 #10760

Open
humitos opened this issue Sep 20, 2023 · 0 comments
Open

Integrations: generic API incoming webhook uses APIv2 #10760

humitos opened this issue Sep 20, 2023 · 0 comments
Labels
Needed: design decision A core team decision is required

Comments

@humitos
Copy link
Member

humitos commented Sep 20, 2023

When creating a "Generic API incoming webhook" it gives you a link and a token to be able to make a request and trigger a build for the project. The URL uses APIv2 which is deprecated and should not be used anymore.

Screenshot_2023-09-20_19-23-26

Now, we have APIv3 that allows triggering builds without creating an incoming webhook. See https://docs.readthedocs.io/en/stable/api/v3.html#build-triggering

There is one noticeable difference between these two:

  • APIv2 uses a token that's valid only for that particular endpoint
  • APIv3 requires a user token
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Needed: design decision A core team decision is required
Projects
Status: Planned
Development

No branches or pull requests

1 participant