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

# Suno Remove Section API Documentation

> Use the Suno remove-section API to delete a selected time range from an existing song while preserving the remaining audio.

<Note>
  This endpoint costs **1 quota (approx. \$0.01)** per request.
</Note>

Submit the source `music_id` and the interval to delete using `crop_start_s` and `crop_end_s`. Save the returned `jobId`, then retrieve the edited song through [Suno Fetch V2](/api/en/suno/suno_fetch_v2) or the `hookUrl` callback.


## OpenAPI

````yaml openapi/en/suno.json POST /suno/v1/remove-section
openapi: 3.1.0
info:
  title: TTAPI API DOCS
  version: 1.0.0
  description: Suno AI Music API
servers:
  - url: https://api.ttapi.io
security: []
paths:
  /suno/v1/remove-section:
    post:
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                music_id:
                  type: string
                  description: Source music ID to edit.
                crop_start_s:
                  type: number
                  description: Start time of the section to remove, in seconds.
                crop_end_s:
                  type: number
                  description: End time of the section to remove, in seconds.
                isStorage:
                  type: boolean
                  default: true
                  description: >-
                    Whether to store the edited audio and return a TTAPI CDN
                    URL.
                hookUrl:
                  type: string
                  description: Callback URL for task updates and results.
              required:
                - music_id
                - crop_start_s
                - crop_end_s
      responses:
        '200':
          $ref: '#/components/responses/SuccessResponse'
        '400':
          $ref: '#/components/responses/400Response'
        '401':
          $ref: '#/components/responses/401Response'
      security:
        - CustomApiKey: []
components:
  responses:
    SuccessResponse:
      description: Request successful
      content:
        application/json:
          schema:
            type: object
            properties:
              status:
                type: string
                example: SUCCESS
              message:
                type: string
                example: success
              data:
                type: object
                example:
                  jobId: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
            required:
              - status
              - message
              - data
    400Response:
      description: Parameter error
      content:
        application/json:
          schema:
            type: object
            properties:
              status:
                type: string
                example: FAILED
              message:
                type: string
              data:
                type: object
            required:
              - status
              - message
    401Response:
      description: Authorization failed
      content:
        application/json:
          schema:
            type: object
            properties:
              status:
                type: string
                example: FAILED
              message:
                type: string
                example: Wrong TT-API-KEY or email is not activated.
            required:
              - status
              - message
  securitySchemes:
    CustomApiKey:
      type: apiKey
      in: header
      name: TT-API-KEY
      description: >-
        You can obtain your API key from the <a
        href='https://dashboard.ttapi.io' target='_blank'>TTAPI Dashboard</a>.

````