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

Tessell Conversation API

The Conversation API from Tessell — 3 operation(s) for conversation.

Tessell Conversation API is one of 82 APIs that Tessell 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, and a getting-started guide.

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

Requests are made against a single base URL, {server}.

3 operations 3 paths 6 schemas 1 GET2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0
Base URL
https://api.console.tessell.com
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Tessell Conversation API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (BearerAuth).

Paths & Operations 3

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

Conversation 3
GET
/tickets/v2/{id}/conversations
ticket's conversation
getTicketConversationsV2 2 params → 200default
POST
/tickets/v2/{id}/reply
Post ticket reply
postReplyV2 2 params body → 200default
POST
/tickets/v2/{id}/notes
Post ticket notes
postNotesV2 2 params body → 200default

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are ApiError (7 properties), ConversationDTOV2 (6 properties), AttachmentDTO (5 properties), ReplyTicketRequestBodyV2 (2 properties). Each schema is shown below with its type and property counts.

ReplyTicketRequestBodyV2
object
Reply to ticket body
2 properties
ConversationDTOV2
object
Ticket conversation DTO
6 properties
ApiError
object
Common error response object for non 2xx responses
7 properties
TicketConversationResponseV2
array
array of conversations
AttachmentDTO
object
Conversation attachment
5 properties
NoteTicketRequestBodyV2
object
Note to ticket body
1 property

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

tessell-conversation-api-openapi.yml Raw ↑

Other APIs Tessell publishes across the network.

Tessell activity-center API
Tessell Ad Domain API
Tessell Ad Domain Governance API
Tessell agentController API
Tessell alert-controller API
Tessell Authorization API
Tessell Availability Machine API
Tessell azure-netapp-admin-controller API
Tessell azure-netapp-service-controller API
Tessell cloud-resource API
Tessell Compute API
Tessell Compute Governance API
Where this information came from

This is an independent, third-party profile of Tessell 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.