Repository navigation
Conversation
|
|
kong
Bot
force-pushed
the
chore/sync-openapi
branch
14 times, most recently
from
October 29, 2026 20:18
eeed2d9 to
a82f95d
Compare
kong
Bot
force-pushed
the
chore/sync-openapi
branch
14 times, most recently
from
October 30, 2026 20:59
9432da9 to
5d95aac
Compare
kong
Bot
force-pushed
the
chore/sync-openapi
branch
29 times, most recently
from
November 6, 2026 00:33
3188e2c to
8571653
Compare
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
API change report
Public API
New Endpoints: 60
POST /forks
GET /lavaflow/global-skills
POST /lavaflow/held-fix-opens
GET /lavaflow/resources
GET /lavaflow/runs
POST /lavaflow/runs
GET /lavaflow/runs/{run_id}
GET /lavaflow/scans
GET /lavaflow/settings
PATCH /lavaflow/settings
PUT /lavaflow/settings
GET /lavaflow/skill-versions
GET /lavaflow/skills
DELETE /lavaflow/skills/{skill_id}
GET /lavaflow/skills/{skill_id}
PATCH /lavaflow/skills/{skill_id}
GET /lavaflow/slack-channels
POST /lavaflow/slack-channels
DELETE /lavaflow/slack-channels/{binding_id}
GET /lavaflow/stats
GET /projects/{id}/capabilities
GET /projects/{id}/databases/{databaseName}/migration-runs
POST /projects/{id}/databases/{databaseName}/migration-runs
GET /projects/{id}/databases/{databaseName}/migration-runs/{runId}
GET /projects/{id}/databases/{databaseName}/migrations
POST /projects/{id}/databases/{databaseName}/migrations/baseline
GET /projects/{id}/frontends/{frontendId}/candidates
POST /projects/{id}/frontends/{frontendId}/candidates
DELETE /projects/{id}/frontends/{frontendId}/candidates/{candidateId}
GET /projects/{id}/frontends/{frontendId}/candidates/{candidateId}
POST /projects/{id}/frontends/{frontendId}/candidates/{candidateId}/deployments
POST /projects/{id}/frontends/{frontendId}/candidates/{candidateId}/promote
GET /projects/{id}/frontends/{frontendId}/serving
POST /projects/{id}/frontends/{frontendId}/serving/rollback
GET /projects/{id}/git-connection/owner-push
GET /projects/{id}/git-deployment-runs
GET /projects/{id}/git-deployment-runs/{runId}
POST /sandbox-file-archives
POST /sandbox-file-parts
GET /sandbox-session-files
GET /share-previews/{share_id}
GET /share-release-drafts
GET /share-releases
POST /share-releases
GET /share-stats
GET /shares
POST /shares
DELETE /shares/{share_id}
GET /shares/{share_id}
PATCH /shares/{share_id}
GET /slack/callback
DELETE /user/sessions
GET /user/sessions
DELETE /user/sessions/{sessionId}
GET /user/slack/channels
GET /user/slack/connections
POST /user/slack/connections
DELETE /user/slack/connections/{connectionId}
POST /user/slack/installations
DELETE /user/tokens/current
Deleted Endpoints: 5
GET /projects/{id}/autofix
PUT /projects/{id}/autofix
GET /projects/{id}/autofix-runs
GET /projects/{id}/autofix-runs/{runId}
POST /projects/{id}/issues/{issueId}/autofix-runs
Modified Endpoints: 286
POST /auth/device/token
access_denied- the approving account's email domain is not inallowed_email_domainswhileallowed_email_domains_modeissignup_and_signin. Re-checked here because approval and redemptionare separate requests.
' to '
access_denied- the approving account's canonical email, or the emailof any of its identities, is not in
allowed_email_domainswhileallowed_email_domains_modeissignup_and_signin. Re-checked here because approval and redemptionare separate requests.
'
POST /auth/device/verify
plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'POST /auth/forgot-password
plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'POST /auth/logout
plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'POST /auth/oauth/exchange
in
allowed_email_domainswhileallowed_email_domains_modeissignup_and_signin. Both are re-checked here because the code outlivesthe callback that issued it.
' to 'Email confirmation is now required, or the account's canonical email or
the provider identity's email is not in
allowed_email_domainswhileallowed_email_domains_modeissignup_and_signin. Both are re-checked here because the code outlivesthe callback that issued it.
'
GET /auth/oauth/providers
user's own account ID at each provider. Match on
provider_user_id,which never changes, rather than on the login or email. For
GitHub, it is the numeric user ID that GitHub reports elsewhere, such
as a webhook's
sender.id.'
plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'POST /auth/oauth/{provider}/call-api
plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'GET /auth/oauth/{provider}/callback
flow's stored redirect_url is no longer registered in
allowed_redirect_urls (re-checked at callback time)
' to 'Missing/invalid code or state, the state parameter expired, the
provider was disabled after the flow started, or the flow's stored
redirect_url is no longer registered in allowed_redirect_urls (both
re-checked at callback time)
'
allowed_email_domains. Creatingan account is refused under
signupandsignup_and_signin; signing inan already-linked account is refused under
signup_and_signin.' to 'The provider's email domain is not in
allowed_email_domains. Creatingan account is refused under
signupandsignup_and_signin; signing inan already-linked account is refused under
signup_and_signin, as it iswhen the account's canonical email is outside the list. A new account
at a reserved domain (
anonymous.volcano.internal,volcano.local) isrefused whatever the project allows.
'
POST /auth/oauth/{provider}/link
plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'POST /auth/oauth/{provider}/refresh-token
plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'GET /auth/oauth/{provider}/token
plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'DELETE /auth/oauth/{provider}/unlink
Cannot unlink if it's the only authentication method.
' to 'Remove OAuth provider from user's account. Refused when the account would
have no other way to sign in: another linked OAuth provider that's enabled
for the project, or a password while email/password sign-in is on for the
project (
enable_email_password).'
plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'GET /auth/password-policy
plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.' to 'Stable machine-readable error code when a specific recovery path is available.plan_required(403) means the project owner's plan does not include the requested feature or option; upgrading the plan unlocks it.person_required(403) means a project access token tried to change LavaFlow settings, which only the project's owner changes, with a platform token, or that the change needs the owner's own credential that expires, a project repository, and an owner whose GitHub account can push to it;errorsays which. A 403 without a code leaves the reason unspecified: it can be an access refusal, a reached limit, or a plan check that could not read the owner's plan. Match on the code, not the message text.'plan_required(403) means the project owner's plan doesReport truncated; see the source commit for the complete contract diff.
Validation