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

# Answer the follow-up

> The reply to the follow-up question offered by `POST /v1/responses` (`follow_up`). One reply per response, within 15 minutes, with the token from that reply. A reply to "Which podcast?" re-classifies the response with it, so the entity gets filled. Doesn't count toward your monthly allowance. Skipping needs no call. The snippet and `<RumorlyQuestion/>` do this for you.



## OpenAPI

````yaml /openapi.json post /v1/responses/{id}/follow-up
openapi: 3.1.0
info:
  title: Rumorly API
  version: 1.0.0
  description: >-
    Send "how did you hear about us?" answers in; get channels, named entities
    and revenue out. All JSON is snake_case.
servers:
  - url: https://api.rumorly.io
    description: Production
security: []
tags:
  - name: Basics
  - name: Responses
    description: Answers and their classification.
  - name: Taxonomy
    description: Your channels and your dictionary of named entities.
  - name: People
    description: The people who answered.
  - name: Reports
    description: Revenue by self-reported channel.
  - name: Snippet
    description: Endpoints the JS snippet calls.
paths:
  /v1/responses/{id}/follow-up:
    post:
      tags:
        - Snippet
      summary: Answer the follow-up
      description: >-
        The reply to the follow-up question offered by `POST /v1/responses`
        (`follow_up`). One reply per response, within 15 minutes, with the token
        from that reply. A reply to "Which podcast?" re-classifies the response
        with it, so the entity gets filled. Doesn't count toward your monthly
        allowance. Skipping needs no call. The snippet and `<RumorlyQuestion/>`
        do this for you.
      parameters:
        - schema:
            type: string
            format: uuid
          required: true
          name: id
          in: path
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                token:
                  type: string
                  minLength: 1
                  maxLength: 200
                answer:
                  type: string
                  minLength: 1
                  maxLength: 500
              required:
                - token
                - answer
              additionalProperties: false
              example:
                token: 1792663391.Q2hhdEdQVCBzYWlkIGhpIDop…
                answer: Lenny's
      responses:
        '202':
          description: Stored; re-classification follows within seconds.
          content:
            application/json:
              schema:
                type: object
                properties:
                  id:
                    type: string
                    format: uuid
                  status:
                    type: string
                    enum:
                      - pending
                      - classified
                      - needs_review
                      - failed
                  follow_up:
                    type: 'null'
                required:
                  - id
                  - status
                  - follow_up
        '400':
          description: The body or query failed validation; `issues` says which field.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '401':
          description: Missing or invalid API key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '402':
          description: >-
            `plan_required`: your plan doesn't include API access (Growth and
            up; the signup trial does). `no_plan`: the workspace has no active
            plan (trial ended or subscription lapsed) and is paused until one is
            chosen. `quota_exceeded` (POST only): this month's response
            allowance is used up.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '403':
          description: >-
            `follow_up_invalid`: the token isn't this response's.
            `follow_up_expired`: more than 15 minutes passed. Or the Origin is
            not on the publishable key's allow-list.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '404':
          description: No response with that id in your workspace.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '409':
          description: '`follow_up_answered`: this follow-up already has a reply.'
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
        '429':
          description: >-
            Publishable keys only: more than 5 replies in a burst (then 1 every
            6 seconds) from one key and IP. See `Retry-After`.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
      security:
        - publishableKey: []
        - secretKey: []
components:
  schemas:
    Error:
      type: object
      properties:
        error:
          type: string
          example: invalid body
        code:
          type: string
        issues:
          type: array
          items:
            type: object
            properties:
              path:
                type: array
                items:
                  anyOf:
                    - type: string
                    - type: number
              message:
                type: string
            required:
              - path
              - message
      required:
        - error
  securitySchemes:
    publishableKey:
      type: http
      scheme: bearer
      description: >-
        A publishable key (`pk_live_…`). Safe in the browser: it can only create
        responses, and only from the origins you allow-listed.
    secretKey:
      type: http
      scheme: bearer
      description: >-
        A secret key (`sk_live_…` / `sk_test_…`) from Settings → API keys.
        Server-side only.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.