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

# Get research answers for a contact

> Return the research questions asked about one contact, with their answers once available.

Person-level research, as opposed to the company-level questions on the Companies endpoints: use it for what differs between people at the same company, such as which brands or business units someone actually looks after.

Free: the credit is charged when the question is asked.



## OpenAPI

````yaml /reference/openapi.yaml get /v2/contacts/{contactID}/research-questions
openapi: 3.1.0
info:
  title: Tamtam Public API
  version: 2.0.0
servers:
  - url: https://api.tamtam.ai/api
security: []
paths:
  /v2/contacts/{contactID}/research-questions:
    get:
      tags:
        - Contacts
      summary: Get research answers for a contact
      description: >-
        Return the research questions asked about one contact, with their
        answers once available.


        Person-level research, as opposed to the company-level questions on the
        Companies endpoints: use it for what differs between people at the same
        company, such as which brands or business units someone actually looks
        after.


        Free: the credit is charged when the question is asked.
      operationId: get-contact-research-questions
      parameters:
        - description: >-
            Tamtam contact ID, as returned by People search or the contacts
            endpoints.
          in: path
          name: contactID
          required: true
          schema:
            description: >-
              Tamtam contact ID, as returned by People search or the contacts
              endpoints.
            examples:
              - b3c6f5e2-1234-4abc-9def-0123456789ab
            type: string
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/GetContactResearchQuestionsResponseDto'
          description: OK
        default:
          content:
            application/problem+json:
              schema:
                $ref: '#/components/schemas/ErrorModel'
          description: Error
      security:
        - apikeyAuth: []
        - bearerAuth: []
components:
  schemas:
    GetContactResearchQuestionsResponseDto:
      additionalProperties: false
      properties:
        questions:
          description: >-
            Research questions asked about this contact. Empty when none has
            been asked yet.
          items:
            $ref: '#/components/schemas/ContactResearchQuestionDto'
          type:
            - array
            - 'null'
      required:
        - questions
      type: object
    ErrorModel:
      additionalProperties: false
      properties:
        detail:
          description: >-
            A human-readable explanation specific to this occurrence of the
            problem.
          examples:
            - Property foo is required but is missing.
          type: string
        errors:
          description: Optional list of individual error details
          items:
            $ref: '#/components/schemas/ErrorDetail'
          type:
            - array
            - 'null'
        instance:
          description: >-
            A URI reference that identifies the specific occurrence of the
            problem.
          examples:
            - https://example.com/error-log/abc123
          format: uri
          type: string
        status:
          description: HTTP status code
          examples:
            - 400
          format: int64
          type: integer
        title:
          description: >-
            A short, human-readable summary of the problem type. This value
            should not change between occurrences of the error.
          examples:
            - Bad Request
          type: string
        type:
          default: about:blank
          description: A URI reference to human-readable documentation for the error.
          examples:
            - https://example.com/errors/example
          format: uri
          type: string
      type: object
    ContactResearchQuestionDto:
      additionalProperties: false
      properties:
        answer:
          description: The answer, present once the status is COMPLETED.
          type: string
        id:
          description: >-
            ID of the question. Stable across contacts: the same question asked
            about ten people carries one ID.
          examples:
            - b3c6f5e2-1234-4abc-9def-0123456789ab
          type: string
        name:
          description: The column name given to this question.
          examples:
            - Brands managed
          type: string
        question:
          description: The question as configured.
          examples:
            - Which brands does this person look after?
          type: string
        status:
          description: One of COMPLETED, PROCESSING, FAILED.
          examples:
            - COMPLETED
          type: string
        updated_at:
          description: When this question last produced an answer for this contact.
          format: date-time
          type: string
      required:
        - id
        - name
        - question
        - status
      type: object
    ErrorDetail:
      additionalProperties: false
      properties:
        location:
          description: >-
            Where the error occurred, e.g. 'body.items[3].tags' or
            'path.thing-id'
          type: string
        message:
          description: Error message text
          type: string
        value:
          description: The value at the given location
      type: object
  securitySchemes:
    apikeyAuth:
      description: Account API key passed in the Authorization header
      in: header
      name: Authorization
      type: apiKey
    bearerAuth:
      description: Bearer JWT obtained via the OAuth 2.1 authorization flow
      scheme: bearer
      type: http

````