Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we
store it to create your key and to recognise you if you sign in with another
provider. By signing up you are subscribing to the APIs.io and API Evangelist
newsletters — you can unsubscribe from any issue. See our
Privacy Policy and Terms.
openapi: 3.2.0
info:
title: KernelScan Teams API
description: 'Public REST API for KernelScan — the Linux kernel CVE analyzer. Upload a kernel .config and get a CycloneDX VEX report of affecting CVEs, query the CVE database, and manage product analyses. Authenticate with `Authorization: Bearer ks_live_` (create one at /api/auth/api-keys). The same surface is also available over MCP at /mcp/.'
version: 1.0.0
contact:
name: KernelScan Support
url: https://kernelscan.io/docs
email: support@kernelscan.io
termsOfService: https://kernelscan.io/agb
servers:
- url: https://kernelscan.io
tags:
- name: Teams
paths:
/api/teams/me:
get:
tags:
- Teams
summary: Get My Team
description: 'The caller''s team and its members. Any member, not just team admins.
A team admin (or global admin) additionally gets ``pending_invitations``
and ``seats``; for members those keys are absent — the shape contract is
documented on :func:`app.services.team_service.get_team_overview`.'
operationId: get_my_team_api_teams_me_get
responses:
'200':
description: Successful Response
content:
application/json:
schema:
additionalProperties: true
type: object
title: Response Get My Team Api Teams Me Get
patch:
tags:
- Teams
summary: Update My Team
operationId: update_my_team_api_teams_me_patch
responses:
'200':
description: Successful Response
content:
application/json:
schema:
additionalProperties: true
type: object
title: Response Update My Team Api Teams Me Patch
/api/teams/me/members/{user_id}:
delete:
tags:
- Teams
summary: Remove My Team Member
description: 'Unseat a member. Their products stay with the team; they get their own.
Not a deletion — the account survives on a fresh personal team, which is why
this is not gated behind a password confirmation the way
``DELETE /api/auth/account`` is. What it does destroy is the removed member''s
*access* to the team''s products, so it is a team-admin action and is logged.'
operationId: remove_my_team_member_api_teams_me_members__user_id__delete
parameters:
- name: user_id
in: path
required: true
schema:
type: string
title: User Id
responses:
'200':
description: Successful Response
content:
application/json:
schema:
type: object
additionalProperties: true
title: Response Remove My Team Member Api Teams Me Members User Id Delete
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
/api/teams/me/invitations:
post:
tags:
- Teams
summary: Create Team Invitation
description: 'Invite someone into the caller''s team by email.
Two deliberate differences from the personal ``POST /api/auth/invitations``:
* **No ``email_is_registered`` 409.** A personal invite is only a way to
*register*, so inviting an existing user is a dead code. A team invite is
a seat: an existing account accepts the very same code while logged in
(``POST /api/auth/invitations/accept``) and moves in, products following.
* **No ``PER_USER_TOTAL_QUOTA``.** That cap throttles viral registration
growth; a team invite is bounded by something better — the seats the
team''s plan actually has (the ``ensure_seat_available`` call below).
Member-only on purpose: ``invited_team_role`` is pinned to ``team_member``
here, promotions stay a staff action in the admin console.'
operationId: create_team_invitation_api_teams_me_invitations_post
responses:
'201':
description: Successful Response
content:
application/json:
schema:
additionalProperties: true
type: object
title: Response Create Team Invitation Api Teams Me Invitations Post
/api/teams/me/invitations/{invitation_id}/revoke:
post:
tags:
- Teams
summary: Revoke Team Invitation
description: 'Withdraw a pending invite and free its seat.
404 for any code that is not THIS team''s — other teams'' codes and personal
invites (``team_id`` NULL) alike: confirming a foreign invitation id exists
is the same disclosure the cross-user product and job routes refuse, and
personal invites keep their existing admin-only revoke. 409 once accepted:
the invitee is a member now, and unseating members is
``DELETE /api/teams/me/members/{id}``, which has rules of its own.'
operationId: revoke_team_invitation_api_teams_me_invitations__invitation_id__revoke_post
parameters:
- name: invitation_id
in: path
required: true
schema:
type: string
title: Invitation Id
responses:
'200':
description: Successful Response
content:
application/json:
schema:
type: object
additionalProperties: true
title: Response Revoke Team Invitation Api Teams Me Invitations Invitation Id Revoke Post
'422':
description: Validation Error
content:
application/json:
schema:
$ref: '#/components/schemas/HTTPValidationError'
components:
schemas:
ValidationError:
properties:
loc:
items:
anyOf:
- type: string
- type: integer
type: array
title: Location
msg:
type: string
title: Message
type:
type: string
title: Error Type
type: object
required:
- loc
- msg
- type
title: ValidationError
HTTPValidationError:
properties:
detail:
items:
$ref: '#/components/schemas/ValidationError'
type: array
title: Detail
type: object
title: HTTPValidationError
externalDocs:
description: KernelScan documentation
url: https://kernelscan.io/docs