How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Socket alerts API

The alerts API from Socket — 4 operation(s) for alerts.

Socket alerts API is one of 19 APIs that Socket publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 3 JSON Schema definitions.

Tagged areas include Alerts. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 3 JSON Schemas.

This API exposes 4 operations across 4 paths, and defines 5 schemas. It is described by OpenAPI 3.2.0, at version 0.

Requests are made against a single base URL, https://api.socket.dev/v0.

4 operations 4 paths 5 schemas 4 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0
Server
https://api.socket.dev/v0
Authentication
HTTP Bearer, HTTP Basic
Resource Areas
1

Authentication & Security 2

Socket alerts API declares 2 security schemes for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). It accepts HTTP basic authentication (basicAuth).

  • bearerAuth — Organization Tokens can be passed as a Bearer token
  • basicAuth — Organization Tokens can be passed as the user field in basic auth

Paths & Operations 4

Across 4 paths, the API surfaces 4 operations — 4 GET. Each is listed below with its method, path, parameters, and response codes.

alerts 4
GET
/orgs/{org_slug}/historical/alerts
List historical alerts (Beta)
historicalAlertsList 55 params → 200400401403404429
GET
/orgs/{org_slug}/historical/alerts/trend
Trend of historical alerts (Beta)
historicalAlertsTrend 54 params → 200400401403404429
GET
/orgs/{org_slug}/alerts
List latest alerts (Beta)
alertsList 70 params → 200400401403404429
GET
/orgs/{org_slug}/alert-full-scan-search
List full scans associated with alert (Beta)
alertFullScans 5 params → 200400401403404429

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Capabilities (7 properties), SocketScore (6 properties), SocketManifestReference (3 properties). Each schema is shown below with its type and property counts.

SocketManifestReference
object
3 properties 1 required
Capabilities
object
7 properties 7 required
SocketId
string
SocketScore
object
6 properties 6 required
Qualifiers

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

socket-dev-alerts-api-openapi.yml Raw ↑

Other APIs Socket publishes across the network.

Socket api-tokens API
Socket audit-log API
Socket dependencies API
Socket diff-scans API
Socket fixes API
Socket full-scans API
Socket license-policy API
Socket metadata API
Socket org-settings API
Socket org-snapshots API
Socket packages API
Socket repo-labels API
Where this information came from

This is an independent, third-party profile of Socket alerts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.