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

Cisco Crosswork Image Controller API

Image Controller

Cisco Crosswork Image Controller API is one of 99 APIs that Cisco Crosswork publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include image-controller. The published artifact set on APIs.io includes an OpenAPI specification.

This API exposes 6 operations across 3 paths, and defines 2 schemas. It is described by OpenAPI 3.2.0, at version 1.0.

Requests are made against a single base URL, /crosswork/imagesvc/.

6 operations 3 paths 2 schemas 2 DELETE3 GET1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://{crosswork-host}:{port}/crosswork/imagesvc/
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Cisco Crosswork Image Controller API declares 1 security scheme for authenticating requests. An API key is passed in the header as Authorization (bearerAuth). By default, every request must be authenticated.

Paths & Operations 6

Across 3 paths, the API surfaces 6 operations — 2 DELETE, 3 GET, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

image-controller 6

Image Controller

GET
/v1/images
Get images
getAllImagesUsingGET 11 params → 200401403404
DELETE
/v1/images
Delete images by id list
deleteImagesByIdListUsingDELETE body → 200204401403
GET
/v1/images/{imageId}
Get image by id
getImageByIdUsingGET 2 params → 200401403404
PUT
/v1/images/{imageId}
Update metadata of image
updateImageInfoUsingPUT 1 param body → 200201401403404
DELETE
/v1/images/{imageId}
Delete image by id
deleteImageByIdUsingDELETE 1 param → 200204401403
GET
/v1/images/count
Get total count of images
getImageCountUsingGET → 200401403404

Schemas 2

The contract defines 2 schemas that model the data the API accepts and returns. The most detailed are ImageDto (11 properties), ResponseDto_ImageDto (3 properties). Each schema is shown below with its type and property counts.

ResponseDto_ImageDto
object
3 properties
ImageDto
object
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-crosswork-image-controller-api-openapi.yml Raw ↑

Other APIs Cisco Crosswork publishes across the network.

Cisco Crosswork Add Credentials API
Cisco Crosswork Add Data Gateway Enrollments API
Cisco Crosswork Add Destinations API
Cisco Crosswork Add Nodes/Devices API
Cisco Crosswork Add Policies API
Cisco Crosswork Add Providers API
Cisco Crosswork Add Tags API
Cisco Crosswork Add via CSV file API
Cisco Crosswork Alarms API
Cisco Crosswork Alert API API
Cisco Crosswork API Controller API
Cisco Crosswork Authconfig API
Where this information came from

This is an independent, third-party profile of Cisco Crosswork Image Controller 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.