Agents

Confirm Agent Session Card

Answer a confirm card the agent posted into a session.

Onboarding runs stop on these ("is this your company?", "are these your competitors?") and resume when the answer lands, usually within ten seconds. Idempotent for the same state.

post/agent/sessions/{session_id}/cards/{card_id}/confirm

Request

  • Base URL: https://be.graph8.com/api/v1
  • URL: https://be.graph8.com/api/v1/agent/sessions/{session_id}/cards/{card_id}/confirm
  • Auth: HTTP bearer

Path parameters

session_idstring required

Session id (UUID).

card_idstring required

The card's id in the session.

Headers

Authorizationstring nullable
X-Target-Org-Idstring nullable

Request body

state'approved' | 'edited' | 'rejected' required

approved accepts the card as proposed, edited accepts it with your edits, rejected sends it back. Re-sending the same state is a no-op; a different state overwrites.

notestring nullable

Why, in your words.

editsobject nullable

Per-field overrides for an edited card. The shape is the card's own and varies by card kind.

Response

Successful Response

dataAgentConversationPayload required

An open envelope for the app's answer.

Open because the chat answer (kind, message, chips, sources, work_item_id, ...) and the oversight feed (approvals, blockers, autonomous_fixes, states, bounds) are both still growing, and a dropped field on an agent surface is one the caller does not know they lost.

Changes

No recorded changes to this operation across all 2 revisions of this API.