> ## Documentation Index > Fetch the complete documentation index at: https://www.pickfu.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Get follow-up answers > Returns paginated follow-up answers for a survey. Each item is a respondent's reply to a follow-up question that was previously sent via `POST /v1/surveys/{id}/responses/{responseId}/followup`. Use the `response_id` query parameter to filter to follow-ups for a single original response. Items where `refunded: true` indicate the follow-up was not delivered (e.g. the respondent declined or the request expired) and the credit was refunded. ## OpenAPI ````yaml /api-reference/openapi.json get /surveys/{id}/followup-answers openapi: 3.1.0 info: title: PickFu API version: 1.0.0 description: >- The PickFu API enables programmatic access to create surveys, retrieve results, and integrate PickFu into your workflows. ## Overview PickFu helps you get instant consumer feedback through surveys. With the API, you can: - Create surveys programmatically - Retrieve survey results and respondent data - Target specific audiences with demographic traits - Integrate PickFu into your product development workflow ## Rate Limits Selected endpoints (currently the CSV export endpoints) enforce per-caller rate limits and return `429 Too Many Requests` when exceeded. See each endpoint description for its specific budget. ## Authentication All API requests require a Bearer token — either an API key or an OAuth 2.0 access token. See the [Authentication guide](https://www.pickfu.com/docs/developers/authentication) for details. contact: name: PickFu Support email: support@pickfu.com url: https://www.pickfu.com servers: - url: https://api.pickfu.com/v1 description: Production - url: https://api.pickfu-sandbox.com/v1 description: Sandbox security: - bearerAuth: [] tags: - name: Surveys description: >- Create, retrieve, update, and publish surveys. Surveys are the core resource — each contains one or more questions with answer options. - name: Responses description: >- Retrieve individual responses (answers) for a survey, with pagination and per-question filtering. - name: Tags description: Organize surveys with tags. Tags are scoped to your team/account. - name: Projects description: >- Organize surveys into projects. Projects group related surveys and can be bookmarked or archived. - name: Traits description: >- Audience targeting and reporting traits used to reach specific demographics and segment survey results. - name: Playbooks description: >- Discover and retrieve step-by-step research playbooks. Each playbook is a structured sequence of polls designed for a specific research goal. - name: Help description: Search the PickFu help center for articles and guides. - name: Media description: >- Generate images from text prompts and upload media files to the PickFu CDN. paths: /surveys/{id}/followup-answers: get: tags: - Surveys summary: Get follow-up answers description: >- Returns paginated follow-up answers for a survey. Each item is a respondent's reply to a follow-up question that was previously sent via `POST /v1/surveys/{id}/responses/{responseId}/followup`. Use the `response_id` query parameter to filter to follow-ups for a single original response. Items where `refunded: true` indicate the follow-up was not delivered (e.g. the respondent declined or the request expired) and the credit was refunded. operationId: getFollowupAnswers parameters: - schema: type: integer minimum: 1 default: 1 in: query name: page required: false description: Page number - schema: type: integer minimum: 1 maximum: 100 default: 25 in: query name: limit required: false description: Results per page (1-100) - schema: type: string in: query name: response_id required: false description: >- Filter follow-up answers to a single original response by its GUID. Use the `id` field returned by GET /v1/surveys/{id}/responses. - schema: type: string in: path name: id required: true description: Survey ID (GUID) responses: '200': description: Default Response content: application/json: schema: type: object properties: data: type: array description: List of follow-up answers items: type: object properties: responseId: type: string description: >- GUID of the original response (parent) this follow-up was sent for questionId: type: string nullable: true description: >- GUID of the original question the parent response was for (multi-question surveys only) question: type: string description: The follow-up question that was sent answer: type: string nullable: true description: The respondent's answer to the follow-up question respondedAt: type: string nullable: true description: >- When the respondent answered the follow-up (ISO 8601) refunded: type: boolean description: >- True when the follow-up was not delivered (e.g. respondent declined or the request expired). The credit charged is refunded. pagination: type: object description: Pagination metadata properties: page: type: number description: Current page number limit: type: number description: Results per page total: type: number description: Total number of results totalPages: type: number description: Total number of pages '401': description: Default Response content: application/json: schema: type: string '403': description: Default Response content: application/json: schema: type: object properties: error: type: string message: type: string '404': description: Default Response content: application/json: schema: type: object properties: error: type: string message: type: string components: securitySchemes: bearerAuth: type: http scheme: bearer bearerFormat: JWT description: >- OAuth2 access token obtained via the authorization flow. Include in the Authorization header as: `Bearer {access_token}` ````