> ## Documentation Index
> Fetch the complete documentation index at: https://docs.correl8.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Post a research study answer

> Custom REST integration for posting research answers

```
POST /v1/project/{project_id}/research/studies/{study_id}/answers/
```

Same payload as the MCP **`post_research_answer`** tool. The study is identified by **UUID in the path** (from the Correl8 app when the study was created). MCP uses a 0-based **`study_index`** in the **`studies`** array returned by **`get_active_studies`** instead.

For the full schema, see **Post a research study answer** in the [API reference](/api-reference/introduction).

## Request

```bash theme={null}
curl -X POST "https://api.correl8.ai/v1/project/{project_id}/research/studies/{study_id}/answers/" \
  -H "Authorization: ApiKey c8.xxx" \
  -H "Content-Type: application/json" \
  -d '{
    "user_id": "user-42",
    "interaction_id": "conv_9f3a2b1c",
    "answer": "The user said they could not find the invite button and expected it on the team settings page."
  }'
```

## Fields

| Field            | Required | Description                                                                                          |
| ---------------- | -------- | ---------------------------------------------------------------------------------------------------- |
| `user_id`        | Yes      | Your identifier for the end user                                                                     |
| `interaction_id` | Yes      | Your identifier for the thread or session                                                            |
| `answer`         | Yes      | Informative summary of what the agent learned (plain prose; include quotes and context when helpful) |

One answer per user per study. Returns **`409`** if that user already answered.

## Response

Returns `201` with `{ "id", "posted_at" }`. Review answers on the study in the [Research](/essentials/using/research) page.