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 Secure Firewall Conversation API

Conversation APIs

Cisco Secure Firewall Conversation API is one of 108 APIs that Cisco Secure Firewall publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Conversation. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, and authentication docs.

This API exposes 16 operations across 12 paths, and defines 29 schemas. It is described by OpenAPI 3.2.0, at version 2.0.0.

Requests are made against a single base URL, https://api.security.cisco.com/api/ai-assistant.

16 operations 12 paths 29 schemas 1 DELETE7 GET1 PATCH4 POST3 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0.0
Base URL
https://api.us.security.cisco.com/firewall
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Cisco Secure Firewall Conversation API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (bearerAuth).

  • bearerAuth — bearer token security scheme

Paths & Operations 16

Across 12 paths, the API surfaces 16 operations — 1 DELETE, 7 GET, 1 PATCH, 4 POST, 3 PUT. Each is listed below with its method, path, parameters, and response codes.

Conversation 16

Conversation APIs

GET
/v2/conversations
List conversations along with details in paginated form
listConversations 7 params → 200400401403404500
POST
/v2/conversations
Create new conversation for a given user
createConversation 1 param body → 200400401403404500
DELETE
/v2/conversations/{conversation_id}
Delete a conversation
deleteConversation 1 param → 200401403404
GET
/v2/conversations/{conversation_id}
Get Conversation details along with chat history for this particular conversation
getConversation 2 params → 200400401403404500
PUT
/v2/conversations/{conversation_id}/addLabel
Add label/s to a conversation's metadata - can be used for filtering
addLabel 2 params body → 200400401403404500
PUT
/v2/conversations/{conversation_id}/description
Update conversation description by providing conversation id
updateConversationDescription 2 params body → 200400401403404500
GET
/v2/conversations/{conversation_id}/history
Retrieve conversation's messages with additional information, in the reverse order of their creation.
listHistory 4 params → 200400401403404500
GET
/v2/conversations/{conversation_id}/message
Retrieve conversation's messages, in the reverse order of their creation.
listMessages 4 params → 200400401403404500
POST
/v2/conversations/{conversation_id}/message
Post request message to an existing active conversation
createMessage 2 params body → 200400401403404500
GET
/v2/conversations/{conversation_id}/message/{message_id}
Retrieve a message using conversationid and messageid
getMessage 3 params → 200400401403404500
GET
/v2/conversations/{conversation_id}/message/{message_id}/feedback
List all feedbacks for a specific message
listFeedback 3 params → 200400401403404500
POST
/v2/conversations/{conversation_id}/message/{message_id}/feedback
Allows for creating an initial feedback object, with Rating, for a particular message
createFeedback 3 params body → 200400401403404500
PATCH
/v2/conversations/{conversation_id}/message/{message_id}/feedback/{feedback_id}
Allows for updating an existing feedback object with quick pick responses and/or freeform response, for a particular message and save said feedback
updateFeedback 4 params body → 200400401403404500
GET
/v2/conversations/{conversation_id}/message/{message_id}/response
Retrieve the response for a given message using conversationid and messageid
getMessageResponse 3 params → 200400401403404500
POST
/v2/conversations/{conversation_id}/message_sse
Post request message to an existing active conversation with streaming response
createMessageSse 2 params body → 200400401403404500
PUT
/v2/conversations/{conversation_id}/removeLabel
Remove label/s from a conversation's metadata
removeLabel 2 params body → 200400401403404500

Schemas 29

The contract defines 29 schemas that model the data the API accepts and returns. The most detailed are message (7 properties), conversation (6 properties), messageFragment (5 properties), messageWithDetails (5 properties). Each schema is shown below with its type and property counts.

postMessageSseResponse
object
create message SSE response body
3 properties 3 required
messageGetResponse
object
get message response body
1 property
createConversationResponse
object
create conversation response body
1 property 1 required
extendedFeedback
object
Extended feedback object
2 properties
conversation
object
Conversation object
6 properties
updateConversationRequest
object
update conversation request body
1 property 1 required
postMessageRequest
object
create message request body
4 properties 2 required
historyListResponse
object
list history response body
1 property
patchFeedbackRequest
object
update feedback request body
1 property
postFeedbackResponse
object
create feedback response body
1 property 1 required
errorResponse
object
error response
3 properties
postMessageResponse
object
create message response body
3 properties 3 required
createConversationRequest
object
create conversation request body
3 properties
message
object
message object
7 properties 1 required
messageListResponse
object
list messages response body
1 property
messageResponseGet
object
get message response body
2 properties
messageFeedback
object
Feedback object
3 properties
removeLabelRequest
object
remove label request body
1 property
taskType
string
task type
pageContext
object
page context
2 properties
label
object
label object
2 properties
postFeedbackRequest
object
create feedback request body
2 properties 1 required
messageStatus
string
message status
listFeedbackResponse
object
List feedback response
1 property
conversationGetResponse
object
get conversation response body
2 properties
addLabelRequest
object
Request to add labels to a conversation
1 property
messageWithDetails
object
message object with additional details
5 properties
messageFragment
object
message fragment
5 properties 2 required
conversationListResponse
object
list conversations response body
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

cisco-secure-firewall-conversation-api-openapi.yml Raw ↑

Other APIs Cisco Secure Firewall publishes across the network.

Cisco Secure Firewall Access Groups API
Cisco Secure Firewall Access Token API
Cisco Secure Firewall Action API
Cisco Secure Firewall Adjacent Zone API
Cisco Secure Firewall AI Assistant API
Cisco Secure Firewall Analysis API
Cisco Secure Firewall API Entitlement API
Cisco Secure Firewall API Keys API
Cisco Secure Firewall App Group API
Cisco Secure Firewall ASA Access Rules API
Cisco Secure Firewall Audit API
Cisco Secure Firewall Audit Logs API
Where this information came from

This is an independent, third-party profile of Cisco Secure Firewall Conversation 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.