Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Koi Security Risk API

Extension risk assessment.

Koi Security Risk API is published by Koi Security on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Risk. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

This API exposes 1 operation across 1 path, and defines 4 schemas. It is described by OpenAPI 3.1.0, at version 1.0.

Requests are made against a single base URL, https://app.extensiontotal.com/api.

1 operations 1 paths 4 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
1.0
Base URL
https://app.extensiontotal.com/api
Authentication
API Key
Contact
Resource Areas
1

Authentication & Security 1

Koi Security Risk API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-Key (ApiKeyAuth). By default, every request must be authenticated, though some operations may also be called without credentials.

  • ApiKeyAuth — Organizational API key issued by Koi. Omit for free, rate-limited anonymous access. Koi's guide documents the header case-insensitively as both X-API-Key and x…

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Risk 1

Extension risk assessment.

POST
/getExtensionRisk
Get the risk assessment for a VS Code extension
getExtensionRisk 1 param body → 200403429

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are ExtensionRisk (5 properties), OrgData (2 properties), ExtensionRiskRequest (2 properties), Error (1 property). Each schema is shown below with its type and property counts.

ExtensionRiskRequest
object
2 properties 1 required
OrgData
object
Optional reporting context attached by the first-party client when organization mode is enabled, so an organization can attribute a finding to the machine and…
2 properties
Error
object
Error condition. Koi's client branches on the HTTP status code and on a plain-string body of Invalid API key; no structured error envelope is documented.
1 property
ExtensionRisk
object
Risk assessment for one extension. Only the fields consumed by Koi's first-party client and named in Koi's published API guide are described here; the live res…
5 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

koi-security-risk-api-openapi.yml Raw ↑