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

# Get workspace usage by day

> Returns the last 30 UTC days of API credit and request counts for the workspace resolved from the API key, oldest first. Unlike the billing- period totals above, this is a fixed trailing window and takes no parameters. Every day in the window is present — a day with no traffic is returned with zero counters rather than omitted.



## OpenAPI

````yaml /api-reference/platform-api.json get /v2/workspace/usage/daily
openapi: 3.0.0
info:
  title: Range Platform API
  description: >-
    The Range Platform API for workspace management, counterparties, and
    operational tooling.
  version: 1.7.19
  contact: {}
servers:
  - url: https://api.range.org
    description: Range API Server
security:
  - Authorization: []
  - Authorization: []
tags:
  - name: Address Information
    description: Get information about a crypto address.
  - name: Transfer Enrichments
    description: Attach workspace-scoped notes and categories to transfers.
  - name: Counterparties
    description: Manage external entities, their addresses, bank accounts, and documents.
paths:
  /v2/workspace/usage/daily:
    get:
      tags:
        - Workspace Usage
      summary: Get workspace usage by day
      description: >-
        Returns the last 30 UTC days of API credit and request counts for the
        workspace resolved from the API key, oldest first. Unlike the billing-
        period totals above, this is a fixed trailing window and takes no
        parameters. Every day in the window is present — a day with no traffic
        is returned with zero counters rather than omitted.
      operationId: getDailyUsage
      parameters: []
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/WorkspaceUsageDailyDto'
components:
  schemas:
    WorkspaceUsageDailyDto:
      type: object
      properties:
        items:
          description: >-
            One entry per day in the window, oldest first. Days with no traffic
            are present with zero counters rather than omitted, so a client can
            plot the series directly without filling gaps itself. The window
            bounds are the first and last entry; they are not repeated as
            separate fields, so there is nothing that can disagree with the
            data.
          type: array
          items:
            $ref: '#/components/schemas/UsageDayDto'
      required:
        - items
    UsageDayDto:
      type: object
      properties:
        date:
          type: string
          description: The UTC calendar day these counters cover (ISO 8601 date)
          example: '2026-08-11'
        credits:
          type: number
          description: Credits consumed on this day across every route
          example: 412
        requests:
          type: number
          description: Requests made on this day across every route
          example: 400
        failed:
          type: number
          description: >-
            Requests on this day that returned 4xx or 5xx. Successful requests
            are `requests - failed` — only failures are counted, so the two can
            never disagree.
          example: 9
        by_family:
          description: This day's counters grouped by operation family
          type: array
          items:
            $ref: '#/components/schemas/UsageByFamilyDto'
        by_route:
          description: This day's counters grouped by exact route
          type: array
          items:
            $ref: '#/components/schemas/UsageByRouteDto'
      required:
        - date
        - credits
        - requests
        - failed
        - by_family
        - by_route
    UsageByFamilyDto:
      type: object
      properties:
        family:
          type: string
          example: risk
        credits:
          type: number
          example: 980
        requests:
          type: number
          example: 950
      required:
        - family
        - credits
        - requests
    UsageByRouteDto:
      type: object
      properties:
        method:
          type: string
          example: GET
        route:
          type: string
          example: /v1/risk/address
        credits:
          type: number
          example: 800
        requests:
          type: number
          example: 800
      required:
        - method
        - route
        - credits
        - requests
  securitySchemes:
    Authorization:
      type: apiKey
      in: header
      name: X-API-KEY
      description: Authorization method required to allow user to access the api endpoints.

````