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

# Get usage transaction details

> Retrieves the details of a usage transaction by its unique `transaction_id`. Returns the subscription, brick, value, timestamp, and any additional properties.



## OpenAPI

````yaml https://api.salesbricks.com/api/v2/openapi.yaml get /usage/transactions/{transaction_id}/
openapi: 3.0.3
info:
  title: Salesbricks REST API
  version: 2.0.0
  description: API reference for external integrations
servers:
  - url: https://api.salesbricks.com/api/v2
    description: Production
  - url: https://api.staging.salesbricks.com/api/v2
    description: Staging
security:
  - ApiKeyAuth: []
tags:
  - name: Subscriptions
    description: >-
      Operations related to subscription management, including creation,
      updates, and retrieving subscription details. Subscriptions can be
      upgraded to add / remove add-ons by using the POST
      /subscriptions/{subscription_id}/upgrade endpoint and can be recasted for
      replacing the current agreement using the POST
      /subscriptions/{subscription_id}/recast endpoint
  - name: Customers
    description: >-
      Operations related to customer management, including creation, updates,
      and managing customer person objects.
  - name: Invoices
    description: Operations related to subscription's invoicing details.
  - name: Plans
    description: >-
      Operations related to listing and getting plan details including bricks in
      the plan.
  - name: Payment Methods
    description: Operations related to subscription's payment method.
paths:
  /usage/transactions/{transaction_id}/:
    get:
      tags:
        - Usage
      summary: Get usage transaction details
      description: >-
        Retrieves the details of a usage transaction by its unique
        `transaction_id`. Returns the subscription, brick, value, timestamp, and
        any additional properties.
      operationId: getUsageTransaction
      parameters:
        - in: path
          name: transaction_id
          schema:
            type: string
            pattern: ^([^/]+)$
          required: true
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UsageEntryDetail'
              examples:
                SuccessResponse:
                  value:
                    transaction_id: tx-12345-abc
                    subscription_id: 550e8400-e29b-41d4-a716-446655440000
                    brick_id: 660e8400-e29b-41d4-a716-446655440001
                    value: '150.000000'
                    time: '2024-01-15T10:30:00Z'
                    properties:
                      region: us-west-2
                      tier: premium
                  summary: Success Response
          description: ''
        '404':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/ErrorResponse'
              examples:
                NotFoundResponse:
                  value:
                    error:
                      code: ERR_NOT_FOUND
                      message: >-
                        Not found — the resource you are looking for does not
                        exist.
                  summary: Not Found Response
          description: ''
components:
  schemas:
    UsageEntryDetail:
      type: object
      description: Response serializer for usage transaction details.
      properties:
        transaction_id:
          type: string
        subscription_id:
          type: string
          format: uuid
        brick_id:
          type: string
          format: uuid
        value:
          type: string
          format: decimal
          pattern: ^-?\d{0,14}(?:\.\d{0,6})?$
        time:
          type: string
          format: date-time
        properties:
          nullable: true
      required:
        - brick_id
        - subscription_id
        - time
        - transaction_id
        - value
    ErrorResponse:
      type: object
      description: >-
        Standardizes API error responses with a consistent structure containing
        error code and message.
      properties:
        error:
          $ref: '#/components/schemas/Error'
      required:
        - error
    Error:
      type: object
      description: >-
        Represents individual error details with a standardized code and
        descriptive message.
      properties:
        code:
          enum:
            - ERR_NOT_FOUND
            - ERR_BAD_REQUEST
            - ERR_SERVER_ERROR
          type: string
          x-spec-enum-id: dc5a5d6feae1b697
          description: >-
            Error code indicating the type of error: NOT_FOUND for missing
            resources, BAD_REQUEST for invalid input, SERVER_ERROR for internal
            server issues


            * `ERR_NOT_FOUND` - ERR_NOT_FOUND

            * `ERR_BAD_REQUEST` - ERR_BAD_REQUEST

            * `ERR_SERVER_ERROR` - ERR_SERVER_ERROR
        message:
          type: string
        error_id:
          type: string
          format: uuid
          description: >-
            Correlation handle for SERVER_ERROR responses — quote this when
            contacting support; it joins to the structured server log line for
            the failure. Not present on 4xx responses.
      required:
        - code
        - message
  securitySchemes:
    ApiKeyAuth:
      type: apiKey
      in: header
      name: X-SALESBRICKS-KEY
      description: API key for authentication

````

## Related topics

- [Delete a usage entry](/api-reference/usage/delete.md)
- [Update a usage entry](/api-reference/usage/patch.md)
- [Submit a usage entry](/api-reference/usage/post.md)