alpha

Send conversations

Ask Alpha a question in a conversation on the organization's Alpha credits; a new conversation id starts one. The idempotency key is the turn id: a retry returns the same turn. With Accept: text/event-stream (REST) or an MCP progress token it streams the turn's events, ending with the result; otherwise follow turnId with alpha_turn_events_get (whose last event is the answer), or poll runId with platform_runs_get_v2, then read alpha_conversations_get_v4; alpha_files_list lists what it made. The member's connected tools join where they wrote everything in the conversation, elsewhere only with useConnectors; if someone else writes there while a question without it is admitted, it is refused 409 PRECONDITION_FAILED (connectors_unconfirmed), nothing reserved, and goes without them when sent again. An API key asks as its creator, only in a conversation it started, without connected tools.

post/api/v1/alpha/conversations/send

Request

  • Base URL: https://point11.ai
  • URL: https://point11.ai/api/v1/alpha/conversations/send
  • Auth: one of:
    • HTTP bearer
    • OAuth 2 (authorization code, authorization URL https://auth.point11.ai/oauth2/authorize, token URL https://auth.point11.ai/oauth2/token)

Headers

Point11-Organizationstring uuid

Organization to act in. Required for OAuth bearers; an API key acts in the organization that owns it.

Idempotency-Keystring uuid required

UUID naming this intent. Retry with the same key; reuse for other input is 409.

Request body

regenerateTurnIdstring uuid
questionstring required
effort'low' | 'xhigh' | 'max'
modelstring
intent'presentation' | 'spreadsheet' | 'document' | 'pdf' | 'ads' | 'page' | 'image'
attachmentsstring[]
useConnectorsboolean

Use your own connected tools for this question in a conversation where someone else asked a question, sent a file or owns its project. Without it they are used only where you wrote all of that. Never used by an API key or in a conversation an API key started.

connectorContinuationtrue

Set only on the continuation Point11 writes after a connector approval or connection, never on a question of your own.

conversationIdstring uuid required

Alpha conversation ID; a new UUID starts a conversation

Response

The run's live events. With Accept: text/event-stream, the live events as server-sent events: one progress event per live event, then exactly one result (the output) or error (OperationError). A refusal before the first event is the ordinary JSON error.

Changes

No recorded changes to this operation across all 1 revision of this API.