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

# Activate Transaction

> Immediately activate loyalty points that are currently in a pending state.

## Activate Transaction

This API is used to immediately activate loyalty points that are currently in a pending state, bypassing the configured return window duration. This endpoint overrides that duration and activates the points immediately, making them available for use by the customer without waiting for the pending return window duration to elapse.

This API is especially useful for scenarios where the client determines that the order is confirmed and the points can be safely activated ahead of schedule.

<Info>
  **Note: Once points are activated, the action cannot be reversed via this API.**
</Info>

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


## OpenAPI

````yaml PUT /api/v4.0/integrations/transactions/{transactionId}/activate
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/{transactionId}/activate:
    put:
      description: >-
        This API is used to immediately activate loyalty points that are
        currently in a pending state, bypassing the configured return window
        duration. This endpoint overrides that duration and activates the points
        immediately, making them available for use by the customer without
        waiting for the pending return window duration to elapse. This API is
        especially useful for scenarios where the client determines that the
        order is confirmed and the points can be safely activated ahead of
        schedule. Note: Once points are activated, the action cannot be reversed
        via this API.
      parameters:
        - name: transactionId
          in: path
          required: true
          schema:
            type: string
          description: The transaction id on your system which you want to activate.
      responses:
        '200':
          description: Transaction activated successfully
          content:
            application/json:
              schema:
                type: object
                properties:
                  pointsActivated:
                    type: number
                    description: >-
                      Number of points that has been successfully activated by
                      the transaction
                    example: 50
                  gameballTransactionId:
                    type: number
                    description: The unique identifier for the transaction within Gameball.
                    example: 11035201
                  clientTransactionId:
                    type: string
                    description: >-
                      A unique identifier for a transaction in your system
                      (e.g., order number or invoice number).
                    example: txn54321221
      security:
        - apiKey: []
          secretKey: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
    apiKey:
      type: apiKey
      in: header
      name: apikey
    secretKey:
      type: apiKey
      in: header
      name: secretkey

````