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

# Daily workspace figures for the dashboard charts

> One point per checked day for the last days days and, as previous, for the same number of days before them: the visibility of every tracked keyword of every primary app as one figure, how many of them rank in the top 10, and how many climbed or fell against the app's previous checked day. change compares each app's latest checked day with the day days before it, leaving out an app whose latest check is older than the range: the change in visibility and in the top 10 count (null when no app was checked that day), how many keywords climbed, fell, started ranking or dropped out, how many apps moved and the largest movers. A point counts every app: one that was not checked that day keeps the figures of its latest earlier check, and its moves count only on the days it was checked. days is 7, 30 or 90. bands splits the keywords of each point by rank. apps answers each primary app with its own points, its change over the range and how many of its keywords moved in its last run; stores pools the apps of each store the same way. lastRun compares each app checked on the newest day with the day before it, over the keywords checked on both days. listingChanges lists, per day and app, the fields a primary app changed in its home listing within the range, leaving out what the store decides (featuring, Editors' Choice). appId or store narrows the whole answer to one primary app or to the primary apps of one store.



## OpenAPI

````yaml /api-reference/openapi.json get /portfolio/history
openapi: 3.0.0
info:
  title: asobeast API
  description: >-
    Self-hosted ASO toolkit API. It tracks the apps you import and their
    competitors over time and reads what AsoBeast collected; it is not a bulk
    store lookup.


    A metered instance carries RateLimit-Limit, RateLimit-Remaining and
    RateLimit-Reset on every response, for the tightest limit the request
    touched. A self-hosted instance has no request rate limits and sends no such
    header. Limits are per workspace, so minting more tokens does not buy more
    capacity, and they are sized per plan across three classes: read for stored
    data, write for configuration changes and store for the endpoints that reach
    the App Store or Google Play.


    A 429 carries Retry-After and a rateLimit object naming the window that
    closed, or an aiAllowance object when the workspace has spent the AI calls
    its plan includes this month. A 403 with a quota object means a plan
    capacity limit such as apps or tracked keyword markets, which is a different
    problem from a rate limit. A 402 with an entitlement object means the
    workspace needs a plan.


    Positions are 1-based and null means checked but not found within the
    captured depth, never zero. Daily granularity uses UTC dates.
  version: 1.16.0
  contact: {}
servers:
  - url: http://localhost:3000/api/backend
    description: Web origin proxy
  - url: http://localhost:4000
    description: Direct API
security:
  - personalApiToken: []
tags: []
paths:
  /portfolio/history:
    get:
      tags:
        - analytics
      summary: Daily workspace figures for the dashboard charts
      description: >-
        One point per checked day for the last days days and, as previous, for
        the same number of days before them: the visibility of every tracked
        keyword of every primary app as one figure, how many of them rank in the
        top 10, and how many climbed or fell against the app's previous checked
        day. change compares each app's latest checked day with the day days
        before it, leaving out an app whose latest check is older than the
        range: the change in visibility and in the top 10 count (null when no
        app was checked that day), how many keywords climbed, fell, started
        ranking or dropped out, how many apps moved and the largest movers. A
        point counts every app: one that was not checked that day keeps the
        figures of its latest earlier check, and its moves count only on the
        days it was checked. days is 7, 30 or 90. bands splits the keywords of
        each point by rank. apps answers each primary app with its own points,
        its change over the range and how many of its keywords moved in its last
        run; stores pools the apps of each store the same way. lastRun compares
        each app checked on the newest day with the day before it, over the
        keywords checked on both days. listingChanges lists, per day and app,
        the fields a primary app changed in its home listing within the range,
        leaving out what the store decides (featuring, Editors' Choice). appId
        or store narrows the whole answer to one primary app or to the primary
        apps of one store.
      operationId: PortfolioController_getHistory
      parameters:
        - name: days
          required: false
          in: query
          schema:
            default: 30
            type: number
            enum:
              - 7
              - 30
              - 90
        - name: appId
          required: false
          in: query
          description: Answer for this primary app alone.
          schema:
            type: string
            maxLength: 64
        - name: store
          required: false
          in: query
          description: Answer for the primary apps of this store alone.
          schema:
            enum:
              - APP_STORE
              - GOOGLE_PLAY
            type: string
      responses:
        '200':
          description: ''
          content:
            application/json:
              schema:
                type: object
components:
  securitySchemes:
    personalApiToken:
      scheme: bearer
      bearerFormat: asob
      type: http

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.