> ## 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.

# Edit Transcript Segment

> Replaces a segment's text and speaker: send both every time. Its times don't change. Words you keep, and words you correct one for one (a typo or punctuation), keep their timing; added words and the words of a rewritten phrase have none. The updated segment isn't returned.



## OpenAPI

````yaml /api-reference/openapi.json patch /v2/transcript-jobs/{jobId}/transcripts/{transcriptId}
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/transcript-jobs/{jobId}/transcripts/{transcriptId}:
    patch:
      tags: []
      summary: Edit a transcript segment
      description: >-
        Replaces a segment's text and speaker: send both every time. Its times
        don't change. Words you keep, and words you correct one for one (a typo
        or punctuation), keep their timing; added words and the words of a
        rewritten phrase have none. The updated segment isn't returned.
      parameters:
        - in: path
          name: jobId
          required: true
          description: 'The transcription job: the `jobId` you got when you created it.'
          schema:
            type: string
            format: uuid
            example: 8f0b0a52-3f6e-4a35-9a3a-0b8a6f3c2d11
        - in: path
          name: transcriptId
          required: true
          description: The segment, from List Transcript Segments.
          schema:
            type: string
            format: uuid
            example: 0186333b-6469-4c33-8b8f-b29ef9db0c99
        - in: query
          name: projectId
          required: true
          description: 'Your project''s ID: the project of your API key.'
          schema:
            type: string
            format: uuid
            example: 48f7656f-098b-4c43-b165-7cfd2cc8ac30
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              required:
                - text
                - transcriptSpeakerId
              properties:
                text:
                  type: string
                  minLength: 1
                  maxLength: 10200
                  description: The segment's text, trimmed. 1 to 10,200 characters.
                  example: Hello, and welcome to the show.
                transcriptSpeakerId:
                  type: string
                  format: uuid
                  description: >-
                    The segment's speaker: the same one, or another to reassign
                    it.
                  example: cc3c21c5-e8bc-436a-a9a9-b0385c2b81b0
      responses:
        '200':
          description: Updated.
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    example: true
                  message:
                    type: string
                    example: Transcript updated successfully
                  messageKey:
                    type: string
                    example: TranscriptUpdatedSuccessfully
        '400':
          description: >-
            Invalid body, for example "The Text field cannot be longer than
            10200 characters", or "Invalid Speaker ID" (`InvalidSpeakerId`). A
            `projectId` that isn't your key's project is refused too.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorSchema'
        '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 `transcription:update`),
            or the project is deactivated (changes are refused; reading still
            works).
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorSchema'
        '404':
          description: >-
            The job or the segment doesn't exist in your project, or the segment
            was deleted ("Transcript not found!", `TranscriptNotFound`).
          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.