---
title: "Search survey responses"
url: https://docs.gleap.ai/en/reference/rest-api/search-survey-responses
method: GET
path: "/engagement/surveys/responses/search"
api: "API Reference"
tag: "Engagement Survey"
operationId: "SearchSurveyResponses"
updatedAt: "2026-11-01T18:40:15.677Z"
language: en
---

# Search survey responses

`GET https://api.gleap.io/v3/engagement/surveys/responses/search`

Full-text search over the answers of all the project's survey responses (Surveys 2.0), newest first. Query parameters: `q` (required, 2–100 characters), `surveyId` (optional, narrows to one survey), `status` (optional comma list of `completed`, `partial`, `in_progress`), `limit` (default 10, at most 50). Answers `{ available, hits: [{ id, surveyId, surveyName, status, channel, nps, snippet, contact, createdAt, completedAt }] }`; `available: false` means the search index is not available in this region (use `GET /{surveyId}/responses?q=` per survey instead).

## Authorization

- `Authorization` (header, required): `Bearer <token>`

## Headers

- `project` (string, required)

## Example request

```bash
curl --request GET \
  --url https://api.gleap.io/v3/engagement/surveys/responses/search \
  --header 'Authorization: Bearer <token>' \
  --header 'project: <project>'
```

## Responses

### 200 (`application/json`)

Ok