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

# List Voice Over Types

> The kinds of voice over you can make: `POETRY`: a poem (in Arabic, with rhyme and rhythm). `COMMERCIAL`: an ad, hook to benefits to call to action. `RELIGIOUS`: a calm, spiritual script. `STORIES`: a narrated story. The three prose types aim for 30 to 120 seconds (75 to 220 words).

Needs **Read** on **Voice overs** (`voice_overs:read`).



## OpenAPI

````yaml /api-reference/openapi.json get /v2/voice-overs/use-cases/list
openapi: 3.0.1
info:
  title: Hamsa API
  description: >-
    The Hamsa API: voice agents and their calls, phone numbers, batch calls and
    knowledge bases; speech to text, text to speech, voices and AI content.
  license:
    name: MIT
  version: 1.0.0
servers:
  - url: https://api.tryhamsa.com
security: []
paths:
  /v2/voice-overs/use-cases/list:
    get:
      tags: []
      summary: List voice over types
      description: >-
        The kinds of voice over you can make: `POETRY`: a poem (in Arabic, with
        rhyme and rhythm). `COMMERCIAL`: an ad, hook to benefits to call to
        action. `RELIGIOUS`: a calm, spiritual script. `STORIES`: a narrated
        story. The three prose types aim for 30 to 120 seconds (75 to 220
        words).


        Needs **Read** on **Voice overs** (`voice_overs:read`).
      parameters: []
      responses:
        '200':
          description: The types.
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: true
                  message:
                    type: string
                    example: success
                  data:
                    type: array
                    items:
                      type: string
                      enum:
                        - POETRY
                        - COMMERCIAL
                        - RELIGIOUS
                        - STORIES
                    example:
                      - POETRY
                      - RELIGIOUS
                      - COMMERCIAL
                      - STORIES
        '401':
          description: Missing or invalid API key.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorSchema'
        '403':
          description: The key's scopes don't allow this (it needs `voice_overs:read`).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorSchema'
        '500':
          description: Server Side Error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorSchema'
      security:
        - ApiKeyAuth: []
components:
  schemas:
    ErrorSchema:
      type: object
      properties:
        code:
          type: integer
          description: >-
            Service error code: the HTTP status with a service prefix (for
            example `8404`). Missing when the service has no code for that
            status.
          example: 8404
        message:
          type: string
          description: >-
            What went wrong. Some services (calls and recordings) put the error
            key here, for example `CallNotFoundOrUnavailable`, and send no
            `messageKey`.
          example: Policy not found!
        messageKey:
          type: string
          description: >-
            Stable key for the error, safe to match on in code. Not returned by
            every service.
          example: PolicyNotFound
        params:
          type: object
          additionalProperties: true
          description: >-
            Details for some errors (for example `reason`). Not returned by
            every service.
          example:
            reason: NO_DRAFT
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: Authorization
      description: >-
        Pass the API key in the Authorization header, You need to put Token
        keyword before the API key. e.g. 'Authorization: Token <api-key>'

````

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