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

Aleph Alpha Conversations API

Create, retrieve, update, delete, and list conversations.

Aleph Alpha Conversations API is one of 37 APIs that Aleph Alpha publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Conversations. The published artifact set on APIs.io includes an OpenAPI specification and API documentation.

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

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

7 operations 3 paths 22 schemas 1 DELETE3 GET1 PATCH2 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.4.23
Base URL
https://api.aleph-alpha.com
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Aleph Alpha Conversations API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (HTTPBearer).

Paths & Operations 7

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

Conversations 7

Create, retrieve, update, delete, and list conversations.

POST
/v1/conversations
Create Conversation Endpoint
create_conversation_endpoint_v1_conversations_post body → 200400401403404422425500
GET
/v1/conversations
List Conversations Endpoint
list_conversations_endpoint_v1_conversations_get 5 params → 200400401403404422425500
GET
/v1/conversations/{conversation_id}
Get Conversation Endpoint
get_conversation_endpoint_v1_conversations__conversation_id__get 2 params → 200400401403404422425500
POST
/v1/conversations/{conversation_id}
Update Conversation Endpoint
update_conversation_endpoint_v1_conversations__conversation_id__post 1 param body → 200400401403404422425500
DELETE
/v1/conversations/{conversation_id}
Delete Conversation Endpoint
delete_conversation_endpoint_v1_conversations__conversation_id__delete 2 params → 200400401403404422425500
PATCH
/v1/conversations/{conversation_id}
Recover Conversation Endpoint
recover_conversation_endpoint_v1_conversations__conversation_id__patch 2 params → 200400401403404422425500
GET
/v1/conversations/{conversation_id}/responses
List Conversation Responses Endpoint
list_conversation_responses_endpoint_v1_conversations__conversation_id__responses_get 3 params → 200400401403404422425500

Schemas 22

The contract defines 22 schemas that model the data the API accepts and returns. The most detailed are ConversationResponseItem (35 properties), MCPTool (8 properties), InputItemReasoning (6 properties), InputItemFunctionCall (6 properties). Each schema is shown below with its type and property counts.

Function
object
Function tool definition (client-executed).
5 properties 2 required
CreateConversationRequest
object
Request body for creating a conversation.
1 property
InputItemMcpApprovalRequest
object
5 properties 2 required
InputItemReasoning
object
Input item for reasoning type messages.
6 properties 2 required
InputItemFunctionCall
object
Input item for function call (history reconstruction).
6 properties 1 required
ConversationListResponse
object
Paginated response for listing conversations.
5 properties 2 required
InputItemMcpApprovalResponses
object
6 properties 4 required
InputItemMessage
object
Input item for structured input. Per Open Responses spec, supports: - message type: role + content - functioncall type: callid + name + arguments (for history)…
5 properties 1 required
ConversationResponse
object
API response schema for conversations — excludes internal fields.
5 properties 3 required
UsageInfo
object
Token usage information.
3 properties 3 required
ContentItem
object
Content item in response output. Per Open Responses spec: - type: outputtext, refusal, etc. - text: the actual content - annotations: optional metadata
3 properties 1 required
InputItemFunctionCallOutput
object
Input item for function call (history reconstruction).
5 properties 1 required
UpdateConversationRequest
object
Request body for updating conversation metadata.
1 property 1 required
InputItemMcpCall
object
6 properties 3 required
InputItemMcpListTools
object
4 properties 2 required
ReasoningSummaryItem
object
Summary item for reasoning output messages.
2 properties 2 required
MCPTool
object
MCP hosted tool definition (server-executed).
8 properties 1 required
ErrorResponse
object
Structured error envelope.
1 property 1 required
ConversationRef
object
Minimal conversation reference embedded in response objects.
1 property 1 required
ConversationResponseItem
object
Full response plus tree metadata and user input for conversation listing.
35 properties 8 required
ConversationResponsesList
object
Response for listing all responses in a conversation.
2 properties 1 required
ErrorDetail
object
Structured error detail matching the OpenAI Responses API convention.
4 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

aleph-alpha-conversations-api-openapi.yml Raw ↑

Other APIs Aleph Alpha publishes across the network.

Aleph Alpha API description API
Aleph Alpha Application Traces API
Aleph Alpha Benchmark Executions API
Aleph Alpha Benchmarks API
Aleph Alpha Cluster API
Aleph Alpha Collection API
Aleph Alpha Connectors API
Aleph Alpha Datasets API
Aleph Alpha Document API
Aleph Alpha Downloads API
Aleph Alpha Evaluation Datasets API
Aleph Alpha Events API
Where this information came from

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