> ## Documentation Index > Fetch the complete documentation index at: https://ara-90a60a07.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # List a Reason's messages > Returns the Reason's conversation in order, as listSessionConversation returns its conversation Session's: the opening prompt, each message sent to it, and one reply for every finished turn, failed or cancelled turns included, with `kind` telling them apart. The page is empty, with `session_id` null, until the conversation is opened by its first message. Cursor-paginated: pass `end_cursor` as `after`, and keep polling with it to receive the Reason's next reply. Readable by the Reason's owner and the people it is shared with. Scope: `sessions:read` ## OpenAPI ````yaml /openapi.json get /v3/organizations/{orgId}/reasons/{reasonId}/messages openapi: 3.1.0 info: title: Reason API version: 3.0.0 description: >- The Reason HTTP API. Drive cloud software-engineering agents: open sessions against your repositories, stream their work, and manage the secrets, skills, and automations they run with. Authenticate with a Reason API key sent as a bearer token. New keys use `reason_`; legacy `ara_` keys remain accepted. Every resource is scoped to an organization; resolve your `org_id` once with `GET /v3/self`. servers: - url: https://api.reasonmachines.com security: - reasonApiKey: [] tags: - name: Account description: Verify a key and resolve the organization it belongs to. - name: Reasons description: >- Start here. A Reason is the long-running agent a person keeps: their main Reason and named ones, each with its own instructions, default model and repositories, conversation, Loops and Sessions. Give a Reason work by messaging it (sendReasonMessage) and read its replies with listReasonMessages. - name: Loops description: >- Standing work a Reason does, woken by a schedule or an event: a webhook, a GitHub event or a Slack message. Each wake opens or continues a Session of the Reason; webhook events that share a correlation key continue one Session. - name: Memory description: >- What Reasons remember across Sessions. Each Session starts by reading MEMORY.md (a short index) and the list of topic notes, and reads a note when its topic comes up. `personal` memory belongs to one person (the API key's owner) and only their Sessions read it; `team` memory belongs to the Workspace and every member's Sessions read it. memory:read lists, reads and searches; memory:write writes and deletes, in team memory only for a Workspace owner or admin. - name: Sessions description: >- A Session is one run of work inside a Reason: every Reason message and Loop wake runs in one, and createSession starts one directly for a single unattended task with a pass/fail outcome. Its transcript, events, result and pull request are read here. - name: Skills description: >- Reusable instruction bundles Reason selects semantically from their descriptions for matching agent tasks. - name: Secrets description: >- Encrypted credentials injected into the agent's sandbox. Write-only: values can be set but never read back. - name: Attachments description: >- Files uploaded to the organization and shared with sessions, downloaded via short-lived signed URLs. - name: Repositories description: Connected repositories, their indexing state, and generated wikis. - name: Git Connections description: Linked source-control accounts and the repositories they expose. - name: Machines description: >- Named Workspace queues served by headless workers. Sessions target a Machine by name and wait for a free worker; more workers serve more Sessions concurrently. - name: Devices description: >- Owned Mac and headless Device identity, bounded enrollment and root grants. - name: Cloud Access description: >- Keyless cloud sign-in for sessions: Reason's OIDC issuer facts and the AWS, Google Cloud and Azure connections a workspace trusts, including which run triggers each one signs in. - name: MCP Servers description: >- Org-level Model Context Protocol servers exposed to the agent. Secret values are write-only. - name: Change Request Reviews description: >- Automated senior-engineer reviews posted on pull requests and merge requests. - name: Consumption description: 'Billing-aligned usage: daily consumption and billing cycles.' - name: Metrics description: Aggregate analytics over sessions, change requests, and usage. - name: Audit Logs description: An append-only record of changes made within the organization. - name: Organizations description: The top-level tenant. Create, read, update, and delete organizations. - name: Members description: People in an organization and their pending invites. - name: Roles description: Role assignments that govern what each member can do. - name: Settings description: 'Organization configuration: namespaced settings and the run tag policy.' - name: Provider credentials description: >- Configure Bring-Your-Own-Key (BYOK) API keys and subscription credentials for model providers. Secret values are write-only. - name: Feedback description: Report problems with the API or these docs to the Reason team. - name: Projects description: >- Deprecated: a project is a Reason with the same id. Use the Reasons operations; these remain for existing clients. - name: Automations description: >- The older form of Loops. Prefer the Loops under a Reason (listReasonLoops, createReasonLoop), which take every wake: schedule, webhook, GitHub, Slack. Use these for what Loops do not carry yet: a run's MCP and app tools, and automations not filed under a Reason. paths: /v3/organizations/{orgId}/reasons/{reasonId}/messages: parameters: - $ref: '#/components/parameters/orgId' - name: reasonId description: The Reason id, returned as `id` by `listReasons` and `createReason`. in: path required: true schema: type: string format: uuid get: tags: - Reasons summary: List a Reason's messages description: >- Returns the Reason's conversation in order, as listSessionConversation returns its conversation Session's: the opening prompt, each message sent to it, and one reply for every finished turn, failed or cancelled turns included, with `kind` telling them apart. The page is empty, with `session_id` null, until the conversation is opened by its first message. Cursor-paginated: pass `end_cursor` as `after`, and keep polling with it to receive the Reason's next reply. Readable by the Reason's owner and the people it is shared with. Scope: `sessions:read` operationId: listReasonMessages parameters: - in: query name: first schema: type: integer default: 50 description: How many conversation items one page holds, up to 200. - in: query name: after schema: type: string description: >- Cursor from a previous page's `end_cursor` (or an item's `cursor`): return only what follows it. Keep polling with the last `end_cursor` to receive the Reason's next replies. responses: '200': description: A page of the Reason's conversation. content: application/json: schema: $ref: '#/components/schemas/ReasonMessagePage' '400': description: >- `after` is not a cursor this list could have issued (`invalid_cursor`). '401': $ref: '#/components/responses/Unauthorized' '403': $ref: '#/components/responses/Forbidden' '404': $ref: '#/components/responses/NotFound' '429': $ref: '#/components/responses/RateLimited' security: - reasonApiKey: - sessions:read components: parameters: orgId: name: orgId in: path required: true description: Organization id or slug. Resolve it with `GET /v3/self`. schema: type: string schemas: ReasonMessagePage: type: object properties: items: type: array items: $ref: '#/components/schemas/ConversationItem' has_next_page: type: boolean end_cursor: description: >- The cursor of the last item, or the `after` that was sent when the page is empty; null only when nothing has been read. Keep polling with it after `has_next_page` is false to receive what is said next. type: - string - 'null' reason_id: type: string format: uuid description: The Reason whose conversation this is. session_id: description: >- The Reason's conversation Session; null, with no items, until its first message opens it. type: - string - 'null' required: - items - has_next_page - end_cursor - reason_id - session_id ConversationItem: type: object properties: id: type: string description: Identifies the item across reads. cursor: type: integer description: >- Where a reader stands after this item: pass it as `after` to read what follows. Cursors strictly increase through the list. It is a position in this list only, not a message `seq`, and the same item can carry a different cursor in a later read; use `id` to recognise an item. kind: type: string enum: - prompt - message - reply description: >- `prompt` is the Session's opening prompt, `message` a message in the conversation afterwards, `reply` how a finished turn ended. role: type: string description: >- `user` for the prompt and for a message sent to the Session; `assistant` for a reply, and for a message the agent posted outside a turn's reply (a greeting or a notice). content: type: string description: >- For a reply, the turn's `result_summary`; empty when the turn left none. status: type: string description: >- Replies only: how the turn ended, in the values of the Session's `status`. outcome: description: >- Replies only: the turn's outcome, as the Session's `outcome` reports it for the latest turn. Null when the turn did not succeed and declared none, for example a failed or cancelled turn. oneOf: - type: string enum: - success - failure - action_required - type: 'null' metadata: type: object properties: source: type: string const: subagent description: An automatic child result, not a human follow-up. required: - source attachments: type: array items: type: object description: >- Messages only. Files attached to the opening prompt are not listed here; list them with listSessionAttachments. created_at: type: - string - 'null' format: date-time required: - id - cursor - kind - role - content Error: type: object properties: error: oneOf: - type: string - type: object required: - type - message properties: type: type: string message: type: string request_id: type: - string - 'null' message: type: string required_scope: type: string description: >- The capability required when the request was denied for a missing scope. responses: Unauthorized: description: Missing, invalid, or expired key. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: missing_bearer message: Authorization required Forbidden: description: The key lacks the required scope or role. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: missing_scope required_scope: sessions:read NotFound: description: Resource not found. content: application/json: schema: $ref: '#/components/schemas/Error' example: error: session_not_found RateLimited: description: >- Too many requests. Retry after the number of seconds in the `Retry-After` response header. headers: Retry-After: description: Seconds to wait before retrying. schema: type: integer minimum: 1 required: true content: application/json: schema: $ref: '#/components/schemas/Error' example: error: type: rate_limited message: This API key exceeded its request-rate limit securitySchemes: reasonApiKey: type: http scheme: bearer bearerFormat: 'reason_ (legacy: ara_)' description: >- Your Reason API key from Settings › API keys. New keys use `reason_`; legacy `ara_` keys remain accepted. Keys are capability-scoped: run, mcp:read, mcp:write, secrets:read, secrets:write, sessions:read, sessions:debug, knowledge:read, memory:read, memory:write, skills:read, skills:write, repos:read, repos:write, reviews:read, reviews:write, deployment:read, analytics:read, org:read, org:write, attachments:read, attachments:write, guardrails:read, guardrails:write, network:read, network:write, automations:read, automations:write, agent_auth:read. network:read and network:write are opt-in, excluded from default keys. network:read reads the saved workspace network policy; network:write replaces custom allowed hosts and requires a current organization owner/admin. Legacy project PATCH requests containing network_allowed_hosts also require network:write plus their existing run scope and project management permission; saved project hosts do not affect current session egress. Only owners/admins can mint or manage keys with network:write; keys cannot grant themselves more authority. See /docs/network-policies for replacement semantics and runtime applicability. mcp:write manages MCP server configuration only; it does not authorize remote MCP-tool execution. sessions:read reads sessions, including the assistant, reasoning and tool activity in their events. sessions:debug is privileged: only for organization owners/admins, it expands session events to the full diagnostic projection (diagnostic event kinds, status text and raw event metadata). ```` This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.