# GET /v1/interactions/{interaction_id}

> One item, by its int_ or call_ id: its type (approval, question, connect, handoff, tool_call), what Bash wants to do, the options, when it expires.

In [Interactions API](https://vestra.ai/developers/reference/api/interactions.md): What Bash waits on (approvals, questions, apps to connect, hand-offs, calls to your tools) and the answers.

Send `Authorization: Bearer vk_test_...` on every call.

One item, by its int_ or call_ id: its type (approval, question, connect, handoff, tool_call), what Bash wants to do, the options, when it expires. A handoff carries a snapshot of the page.

Your API key, or a session's token, scope `runtime` or `all`. On the card: [`answer`](https://vestra.ai/developers/answer.md). Every call here is a checked sample.

## Request

Path:

- `interaction_id` (`string`, required): What Bash waits on, by its id: `int_...`, or `call_...` for a call to your tool.

## Answers 200

- `object` (`"interaction"`): Always interaction.
- `id` (`string`): The interaction, to answer by its id (int_...; call_... for a call to your tool). Example: `int_3j9`.
- `user_id` (`string | null`): Your id for the user it is for; null on your company's own Bash.
- `task_id` (`string | null`): The task that asked (task_...); null for a call to your tool that Bash's reply made.
- `conversation_id` (`string | null`): Its conversation (conv_...); null when its task has none.
- `kind` (`"ask_question" | "composio_auth" | "tool_permission" | "credit_approval" | "exit_plan" | "custom" | "hands_approval" | "plan_limit"`): What exactly Bash waits on. ask_question: a question, or a hand-off. composio_auth: connecting an app. tool_permission: a step with a tool. credit_approval: spending on a paid tool. exit_plan: a plan before it starts. hands_approval: an action on a computer, approved in person. plan_limit: a plan's limit ran out (read only). custom: anything else, named by details.renderer.
- `type` (`"approval" | "question" | "connect" | "handoff" | "tool_call"`): What kind of answer it takes. approval: yes or no. question: an answer to each question. connect: your user connects an app. handoff: a person does one thing, then says so. tool_call: your tool returns an output or an error.
- `status` (`"pending" | "resolved" | "cancelled" | "expired"`): pending: Bash waits on it. resolved: it was answered. cancelled: it was withdrawn before an answer. expired: nobody answered in time.
- `summary` (`string`): What Bash wants, in a phrase to show your user. Example: `pay, amount $500.00`.
- `moves_money` (`boolean | null`): Whether saying yes spends money, such as a payment. null on the card for one of your own tools (a function of yours, or a tool of your MCP servers): your app knows what your tools cost, and Vestra cannot.
- `requires_present_user` (`boolean`): Whether a yes needs present_user: true, meaning the person who saw it said yes: true for a payment, and for an action approved in person.
- `nonce` (`string`, may be absent): For an action approved in person (hands_approval) only: send it back with your yes.
- `questions` (`object[]`, may be absent): For a question or a hand-off: what Bash asks, one or more questions.
  - `question` (`string`): The question, as Bash asks it. Example: `Which flight should I book?`.
  - `header` (`string`): A short label for it, for a heading or a chip; empty when Bash gave none.
  - `options` (`object[]`): Answers Bash suggests; your user may still answer in their own words. Empty when it suggests none.
    - `label` (`string`): An answer your user can pick.
    - `description` (`string`): A line more about that answer; empty when there is none.
  - `multi_select` (`boolean`): Whether more than one option may be picked.
- `frame_url` (`string`, may be absent): For a hand-off, on a single read only (never in lists): the page Bash was on when it asked, as a JPEG data URI.
- `browser` (`object`, may be absent): For a hand-off in the browser: open a session with a screen (POST /v1/sessions) so a person can do it.
  - `suggested_mode` (`"control"`): Open the screen with control, so the person can take the wheel.
  - `url` (`string | null`): The page Bash's browser is on; null when it did not say.
- `details` (`map of any`): A few named facts for its kind, safe to show: such as tool_name and rows for a tool step (with server for a tool of an MCP server, and its arguments as rows), or app for a connection. Never the raw request.
- `outcome` (`object | null`): How it ended; null while it is pending.
  - `decision` (`"approved" | "denied" | "answered" | "cancelled" | "expired"`): How it ended.
  - `answers` (`string[]`, may be absent): For an answered question: the answer to each question, in order.
  - `reason` (`string`, may be absent): For a denial: why, when one was recorded.
  - `message` (`string`, may be absent): For a denial: the note that was sent with the no, when there was one.
- `created_at` (`string`): When Bash asked, as an ISO 8601 time.
- `expires_at` (`string | null`): When it expires unanswered, as an ISO 8601 time; null when it never does.
- `resolved_at` (`string | null`): When it was answered, withdrawn or expired, as an ISO 8601 time; null while pending.

## Code

**TypeScript**

```ts
const interaction = await vestra.answer.get('int_3j9');
```

**Python**

```python
interaction = vestra.answer.get("int_3j9")
```

**HTTP**

```bash
# interaction.created names what Bash waits on. Read it, show it to your user, then answer it.
curl "$VESTRA_BASE_URL/v1/interactions/int_3j9" \
  -H "Authorization: Bearer $VESTRA_API_KEY"

curl "$VESTRA_BASE_URL/v1/interactions/int_3j9/answer" \
  -H "Authorization: Bearer $VESTRA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{ "approve": true, "present_user": true }'
```

**CLI, MCP**: No sample in your language for this route, so here it is over HTTP.