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

# Release Hold

> Release held points for redemption or cancel the hold.

<Info>
  Security: Provide both `apikey` and `secretkey` headers.
</Info>


## OpenAPI

````yaml DELETE /api/v4.0/integrations/transactions/hold/{holdReferenceId}
openapi: 3.1.0
info:
  title: Gameball API
  description: >-
    Gameball REST API v4.0 - Complete API reference for integrating loyalty,
    gamification, and customer engagement features
  version: 4.0.0
servers:
  - url: https://api.gameball.co
security:
  - bearerAuth: []
paths:
  /api/v4.0/integrations/transactions/hold/{holdReferenceId}:
    delete:
      description: >-
        This API cancels a specific hold on loyalty points in Gameball using the
        provided holdReferenceId. It releases the held points back into the
        customer's account, enabling flexibility in point management.
      parameters:
        - name: holdReferenceId
          in: path
          required: true
          schema:
            type: string
          description: >-
            Unique identifier for the hold transaction, used to release the held
            points or amount.
      responses:
        '200':
          description: Hold released successfully
          content:
            application/json:
              schema:
                type: object
                properties:
                  success:
                    type: boolean
                    description: Indicates whether the hold was successfully released.
                    example: true
                  message:
                    type: string
                    description: >-
                      Confirmation message indicating the hold has been
                      released.
                    example: Hold released successfully
      security:
        - apiKey: []
          secretKey: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
    apiKey:
      type: apiKey
      in: header
      name: apikey
    secretKey:
      type: apiKey
      in: header
      name: secretkey

````