Cisco Crosswork Event Type API
The Event Type API from Cisco Crosswork — 2 operation(s) for event type.
The Event Type API from Cisco Crosswork — 2 operation(s) for event type.
Every API here is available over the APIs.io API and to AI agents over MCP.
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
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.curl "https://apis.io/api/v1/apis/cisco-crosswork-event-type-api"
curl "https://apis.io/api/v1/apis?limit=25"
Discovery needs no key. Ratings and market analysis are Pro.
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: 3.2.0
info:
description: Cisco Crosswork Workflow Manager (CWM) 2.1 offers RESTful APIs that enable automation engineers and developers to create, deploy, and manage workflows, adapters, jobs, resources, events, and workers within the Cisco CWM platform.
title: Cisco Crosswork Workflow Manager Event Type API
termsOfService: www.cisco.com
contact:
name: API Support
url: https://www.cisco.com/support
version: 2.1.0
x-provenance:
method: harvested
authored_by: Cisco Crosswork
harvested_by: API Evangelist
harvested_on: '2026-08-19'
first_party: true
provider_published: true
note: 'Reconstructed verbatim from the per-operation Swagger 2.0 JSON fragments Cisco serves for the Crosswork Workflow Manager API reference at developer.cisco.com/docs/crosswork/workflow-manager/. info, basePath and securityDefinitions are Cisco''s own meta block; each path/method object is Cisco''s own spec object, unmodified except that inline schemas carrying the swagger-ui $$ref marker were hoisted back into #/definitions and replaced with a real $ref.'
servers:
- url: /crosswork/cwm/v2
tags:
- name: Event Type
paths:
/eventType:
get:
description: Retrieve a list of all registered event types.
tags:
- Event Type
summary: List all event types
operationId: list_event
responses:
'200':
description: Event types retrieved successfully.
content:
application/json:
schema:
type: array
items:
$ref: '#/components/schemas/server.EventResponse'
'400':
description: Bad request.
content:
application/json:
schema:
$ref: '#/components/schemas/gin.H'
'404':
description: Event type not found.
content:
application/json:
schema:
$ref: '#/components/schemas/gin.H'
__originalOperationId: list-event
method: get
path: /eventType
post:
description: Create a new event type. The 'Kind' field can be either "consumed" or "produced".
tags:
- Event Type
summary: Create a new event type
operationId: create_event_type
responses:
'201':
description: Event type created successfully.
content:
application/json:
schema:
type: string
'503':
description: Service unavailable.
content:
application/json:
schema:
$ref: '#/components/schemas/server.HTTPError'
__originalOperationId: create-event-type
method: post
path: /eventType
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/server.EventDefinition'
description: Event type data to create.
required: true
/eventType/{type}/{actionOrKind}:
delete:
description: Delete an existing event type.
tags:
- Event Type
summary: Delete an event type
operationId: delete_event_type
parameters:
- description: The event type name.
name: type
in: path
required: true
schema:
type: string
- description: The event kind.
name: actionOrKind
in: path
required: true
schema:
type: string
responses:
'200':
description: Event type deleted successfully.
content:
application/json:
schema:
type: string
'400':
description: Bad request.
content:
application/json:
schema:
$ref: '#/components/schemas/gin.H'
'404':
description: Event type not found.
content:
application/json:
schema:
$ref: '#/components/schemas/gin.H'
__originalOperationId: delete-event-type
method: delete
path: /eventType/{type}/{actionOrKind}
get:
description: Retrieve detailed information about a specific event type and kind.
tags:
- Event Type
summary: Get a specific event type
operationId: describe_event
parameters:
- description: The event type name.
name: type
in: path
required: true
schema:
type: string
- description: The event kind (consumed or produced).
name: actionOrKind
in: path
required: true
schema:
type: string
responses:
'200':
description: Event type retrieved successfully.
content:
application/json:
schema:
$ref: '#/components/schemas/server.EventResponse'
'400':
description: Bad request.
content:
application/json:
schema:
$ref: '#/components/schemas/gin.H'
'404':
description: Event type not found.
content:
application/json:
schema:
$ref: '#/components/schemas/gin.H'
__originalOperationId: describe-event
method: get
path: /eventType/{type}/{actionOrKind}
post:
description: Start or stop an event listener for a specific event type.
tags:
- Event Type
summary: Manage an event listener
operationId: manage_event_listener
parameters:
- description: The event type name.
name: type
in: path
required: true
schema:
type: string
- description: The action to perform (start or stop).
name: actionOrKind
in: path
required: true
schema:
type: string
responses:
'200':
description: Event listener action performed successfully.
content:
application/json:
schema:
type: string
'400':
description: Bad request.
content:
application/json:
schema:
$ref: '#/components/schemas/gin.H'
'404':
description: Event type not found.
content:
application/json:
schema:
$ref: '#/components/schemas/gin.H'
__originalOperationId: manage-event-listener
method: post
path: /eventType/{type}/{actionOrKind}
put:
description: Update an existing event type's configuration.
tags:
- Event Type
summary: Update an existing event type
operationId: update_event_type
parameters:
- description: The event type name.
name: type
in: path
required: true
schema:
type: string
- description: The event kind.
name: actionOrKind
in: path
required: true
schema:
type: string
responses:
'200':
description: Event type updated successfully.
content:
application/json:
schema:
type: string
'503':
description: Service unavailable.
content:
application/json:
schema:
$ref: '#/components/schemas/server.HTTPError'
__originalOperationId: update-event-type
method: put
path: /eventType/{type}/{actionOrKind}
requestBody:
content:
application/json:
schema:
$ref: '#/components/schemas/server.EventDefinition'
description: Event type data to update.
required: true
components:
schemas:
server.HTTPError:
type: object
properties:
code:
type: integer
example: 400
message:
type: string
example: status bad request
gin.H:
type: object
additionalProperties: {}
server.EventDefinition:
type: object
properties:
correlationAttrs:
type: array
items:
type: integer
createWorkflow:
type: boolean
endpoint:
type: string
kind:
type: string
payloadAttrs:
type: object
additionalProperties:
type: string
resourceId:
type: string
source:
type: string
type:
type: string
workflowName:
type: string
workflowVersion:
type: string
server.EventResponse:
type: object
properties:
correlationAttrs:
type: array
items:
type: integer
createWorkflow:
type: boolean
endpoint:
type: string
internallyManagedListener:
type: boolean
default: false
kind:
type: string
payloadAttrs:
type: object
additionalProperties:
type: string
resourceId:
type: string
source:
type: string
state:
type: boolean
default: false
type:
type: string
workflowName:
type: string
workflowVersion:
type: string
securitySchemes:
Bearer:
type: apiKey
name: Authorization
in: header
description: 'JWT Authorization header using the Bearer scheme. Example: "Authorization: Bearer {token}"'
x-evidence:
- type: reference
url: https://developer.cisco.com/docs/crosswork/workflow-manager/
- type: fragment-index
url: https://pubhub.devnetcloud.com/media/crosswork-workflow-manager-api-document/docs/262737b2-b3c2-32cd-b07b-fdbdcd23918f/apis/
count: 90