Nebulock Findings API

Retrieve and manage security findings and their comments.

Operations 5

GET /api/v2/findings/{finding_id} Retrieve the details for a specific finding. #
PATCH /api/v2/findings/{finding_id} Update an existing finding and return the updated finding. #
GET /api/v2/findings Retrieve all findings within an organization, with pagination metadata. #
GET /api/v2/findings/{finding_id}/comments Retrieve the comments for a finding. #
POST /api/v2/findings/{finding_id}/comments Create a comment for a finding. #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API
curl "https://apis.io/api/v1/apis/nebulock-findings-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

nebulock-findings-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Nebulock Public Entities Findings API
  version: v2
  description: 'Public API for the Nebulock AI threat-hunting platform: Findings, Entities (actors/users/hosts), Hunts, hunt suggestions/reports, and detection Rules. Available to active Nebulock customers. Authentication uses per-organization API keys passed in the X-API-Key-ID and X-API-Key-Secret headers. Rate limit: 60 requests per minute.'
  contact:
    name: Nebulock
    url: https://docs.nebulock.io/
servers:
- url: https://api.nebulock.io
  description: Production
security:
- ApiKeyId: []
  ApiKeySecret: []
tags:
- name: Findings
  description: Retrieve and manage security findings and their comments.
paths:
  /api/v2/findings/{finding_id}:
    get:
      operationId: get_finding_with_details
      summary: Retrieve the details for a specific finding.
      tags:
      - Findings
      responses:
        '200':
          description: Successful response
        '401':
          description: Missing or invalid API key credentials
        '403':
          description: Not permitted for this organization
        '404':
          description: Resource not found
        '422':
          description: Validation error
        '429':
          description: Rate limit exceeded (60 requests per minute)
      parameters:
      - name: finding_id
        in: path
        required: true
        schema:
          type: string
    patch:
      operationId: update_finding
      summary: Update an existing finding and return the updated finding.
      tags:
      - Findings
      responses:
        '200':
          description: Successful response
        '401':
          description: Missing or invalid API key credentials
        '403':
          description: Not permitted for this organization
        '404':
          description: Resource not found
        '422':
          description: Validation error
        '429':
          description: Rate limit exceeded (60 requests per minute)
      parameters:
      - name: finding_id
        in: path
        required: true
        schema:
          type: string
  /api/v2/findings:
    get:
      operationId: list_findings
      summary: Retrieve all findings within an organization, with pagination metadata.
      tags:
      - Findings
      responses:
        '200':
          description: Successful response
        '401':
          description: Missing or invalid API key credentials
        '403':
          description: Not permitted for this organization
        '404':
          description: Resource not found
        '422':
          description: Validation error
        '429':
          description: Rate limit exceeded (60 requests per minute)
  /api/v2/findings/{finding_id}/comments:
    get:
      operationId: get_finding_comments
      summary: Retrieve the comments for a finding.
      tags:
      - Findings
      responses:
        '200':
          description: Successful response
        '401':
          description: Missing or invalid API key credentials
        '403':
          description: Not permitted for this organization
        '404':
          description: Resource not found
        '422':
          description: Validation error
        '429':
          description: Rate limit exceeded (60 requests per minute)
      parameters:
      - name: finding_id
        in: path
        required: true
        schema:
          type: string
    post:
      operationId: create_finding_comment
      summary: Create a comment for a finding.
      tags:
      - Findings
      responses:
        '200':
          description: Successful response
        '401':
          description: Missing or invalid API key credentials
        '403':
          description: Not permitted for this organization
        '404':
          description: Resource not found
        '422':
          description: Validation error
        '429':
          description: Rate limit exceeded (60 requests per minute)
      parameters:
      - name: finding_id
        in: path
        required: true
        schema:
          type: string
components:
  securitySchemes:
    ApiKeyId:
      type: apiKey
      in: header
      name: X-API-Key-ID
    ApiKeySecret:
      type: apiKey
      in: header
      name: X-API-Key-Secret