Cloudsek Events API

The Events API from Cloudsek — 2 operation(s) for events.

Operations 2

PATCH /v2/events/{id}/assignee Reassign an event to a user (by email) #
POST /v2/events/{id}/{idid} Remediate an event (Closed* transition + closure narrative) #

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/cloudsek:cloudsek-events-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"

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

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

OpenAPI Specification

cloudsek-events-api-openapi.yml Raw ↑
openapi: 3.2.0
info:
  title: Cloudsek Events API
  version: '2026-10-09'
  description: 'GENERATED FROM DOCUMENTATION by API Evangelist on 2026-10-09: 11 operation(s) read from 16 public documentation page(s) (each operation names its page in x-source). This is not the provider''s published contract; Cloudsek has published no machine-readable contract that the pipeline could find. Engine: local.'
  x-evidence-tiers:
    code-example: 0
    documentation: 11
    pages-with-code: 0
    pages-read: 16
  x-generated-from: documentation
  x-provenance: generated
  x-authored-by: API Evangelist
  x-generated: '2026-10-09'
  x-generator: generate-contract-from-docs.py
  x-engine: local
  x-sources:
  - https://api.cloudsek.com/docs/api/bulk-jobs
  - https://api.cloudsek.com/docs/api/get-alerts
  - https://api.cloudsek.com/docs/api/patch-event
  - https://api.cloudsek.com/docs/api/events-write
  - https://api.cloudsek.com/docs/api/get-alerts-v-2
  - https://api.cloudsek.com/docs/api/patch-incident
  - https://api.cloudsek.com/docs/api/post-event-bulk
  - https://api.cloudsek.com/docs/api/get-event-snapshot
  - https://api.cloudsek.com/docs/api/post-event-comment
  - https://api.cloudsek.com/docs/api/post-incident-bulk
  - https://api.cloudsek.com/docs/api/get-historic-alerts
  - https://api.cloudsek.com/docs/api/patch-event-assignee
  - https://api.cloudsek.com/docs/api/post-event-remediate
  - https://api.cloudsek.com/docs/api/get-incident-snapshot
  - https://api.cloudsek.com/docs/api/post-incident-comment
  - https://api.cloudsek.com/docs/api/get-historic-alerts-v-2
security:
- Bearer_token: []
tags:
- name: Events
paths:
  /v2/events/{id}/assignee:
    patch:
      operationId: patch_v2_events_id_assignee
      tags:
      - Events
      summary: Reassign an event to a user (by email)
      x-source: https://api.cloudsek.com/docs/api/patch-event-assignee
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      requestBody:
        required: false
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/PatchV2EventsIdAssigneeRequest'
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
  /v2/events/{id}/{idid}:
    post:
      operationId: post_v2_events_id_idid
      tags:
      - Events
      summary: Remediate an event (Closed* transition + closure narrative)
      description: 'Triggers the event''s remediation flow: a transition to a Closed* status combined with a comment. Includes the same rescan-redirect handling as PATCH /v2/events/{id}. The closure comment is always written. Returns the new comment_id or prior operation_id on identical remediation.'
      x-source: https://api.cloudsek.com/docs/api/post-event-remediate
      parameters:
      - name: id
        in: path
        required: true
        schema:
          type: string
      - name: idid
        in: path
        required: true
        schema:
          type: string
      responses:
        '200':
          description: Success (status as documented)
      x-evidence:
        kind: documentation
        collapsed_from: 2 example path(s) differing only at idId
components:
  schemas:
    PatchV2EventsIdAssigneeRequest:
      type: object
      properties:
        assignee_email:
          type: string
          description: Email of the user to assign the event to; set to null to unassign.
  securitySchemes:
    Bearer_token:
      type: http
      scheme: bearer
      x-source: https://api.cloudsek.com/docs/intro/