> ## Documentation Index
> Fetch the complete documentation index at: https://na-36-changelog-go-livepeer-2026-05-18.mintlify.site/llms.txt
> Use this file to discover all available pages before exploring further.

# Rebond

> Rebond for Livepeer gateways.



## OpenAPI

````yaml POST /rebond
openapi: 3.0.3
info:
  title: Livepeer CLI Local HTTP API
  description: |
    Local control-plane HTTP endpoints exposed by the Livepeer node.

    The CLI HTTP API provides programmatic access to node management functions
    including status monitoring, staking operations, orchestrator configuration,
    and broadcast settings.

    **Default Ports:**
    - Gateway: http://localhost:5935
    - Orchestrator: http://localhost:7935
  version: 1.0.0
  contact:
    name: Livepeer Documentation
    url: https://docs.livepeer.org
servers:
  - url: http://localhost:5935
    description: Gateway CLI API (default)
  - url: http://localhost:7935
    description: Orchestrator CLI API
security: []
tags:
  - name: Status
    description: Node status and information
  - name: Staking
    description: Token bonding and delegation operations
  - name: Orchestrator
    description: Orchestrator configuration and management
  - name: Gateway
    description: Gateway/broadcaster configuration
  - name: Ethereum
    description: Ethereum operations and token transfers
paths:
  /rebond:
    post:
      tags:
        - Staking
      summary: Rebond tokens
      description: Rebond tokens in unbonding state
      operationId: rebondTokens
      requestBody:
        required: true
        content:
          application/json:
            schema:
              type: object
              properties:
                unbondingLockId:
                  type: integer
                  description: ID of the unbonding lock to rebond
                  example: 0
      responses:
        '200':
          description: Rebond successful
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/TransactionResponse'
components:
  schemas:
    TransactionResponse:
      type: object
      properties:
        txHash:
          type: string
          description: Transaction hash
          example: 0x...
        status:
          type: string
          description: Transaction status
          example: success

````