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

# Ticker Trend List Data

> Retrieve a list of trending tickers based on various metrics. Returns securities ordered by trending score across different time intervals.

<ResponseExample>
  ```json Response (200 OK) theme={null}
  {
    "ok": true,
    "data": [
      {
        "security": {
          "ticker": "RVLV",
          "name": "Revolve Gr",
          "exchange": "NYSE"
        },
        "count": 2344,
        "pct_chg": 23340
      }
    ]
  }
  ```
</ResponseExample>

<ResponseExample>
  ```json Response (400 Bad Request) theme={null}
  {
      "ok": false,
      "errors": [
          {
              "id": "hbiGJjhsSpnfhM8aBePyTB",
              "code": "400",
              "value": "Bad Request"
          }
      ]
  }
  ```
</ResponseExample>

<ResponseExample>
  ```json Response (500 Internal Server Error) theme={null}
  {
      "ok": false,
      "errors": [
          {
              "id": "hbiGJjhsSpnfhM8aBePyTB",
              "code": "500",
              "value": "Something went wrong"
          }
      ]
  }
  ```
</ResponseExample>


## OpenAPI

````yaml /openapi/ticker-trends-api_api.spec.yml GET /api/v1/trending-tickers/list
openapi: 3.0.0
info:
  contact: {}
  description: >-
    This REST API provides endpoints to search for trending tickers and get
    ticker details.
  termsOfService: http://swagger.io/terms/
  title: TickerTrends API
  version: 2.1.0
servers:
  - url: https://api.benzinga.com
    description: PROD
security: []
paths:
  /api/v1/trending-tickers/list:
    get:
      tags:
        - Ticker Trends
      summary: Get Trending Tickers List
      description: >-
        Retrieve a list of trending tickers based on various metrics. Returns
        securities ordered by trending score across different time intervals.
      operationId: get-ticker-trend-list-data
      parameters:
        - description: >-
            Deprecated. Use timeframe instead. Time interval for aggregating
            trend data.
          in: query
          name: interval
          required: true
          schema:
            type: string
        - description: >-
            Optional comma-separated list of ticker symbols to filter results.
            If omitted, returns all trending tickers.
          in: query
          name: tickers
          schema:
            type: string
        - description: >-
            Data source filter for trend calculation. Supported values: all (all
            sources combined), clickstream (user interaction data), logo (logo
            request data). Required.
          in: query
          name: source
          required: true
          schema:
            type: string
        - description: >-
            Time interval for trend aggregation. Supported values: 10m (10
            minutes), 1h (1 hour), 1d (1 day). Default: 1d
          in: query
          name: timeframe
          schema:
            type: string
        - description: >-
            Start time filter in 24-hour format (e.g., 09:15, 14:30). Use with
            date_from for precise time ranges.
          in: query
          name: time_from
          schema:
            type: string
        - description: >-
            End time filter in 24-hour format (e.g., 16:00, 22:30). Use with
            date_to for precise time ranges.
          in: query
          name: time_to
          schema:
            type: string
        - description: >-
            Start date filter in ISO 8601 format (e.g., 2024-12-30, 2024-01-15).
            Use with time_from for precise ranges.
          in: query
          name: date_from
          schema:
            type: string
        - description: >-
            End date filter in ISO 8601 format (e.g., 2024-12-30, 2024-01-31).
            Use with time_to for precise ranges.
          in: query
          name: date_to
          schema:
            type: string
        - description: >-
            Page number for pagination. Zero-indexed (0 = first page, 1 = second
            page, etc.). Default: 0
          in: query
          name: page
          schema:
            type: integer
        - description: 'Number of results per page. Default: 1000. Maximum: 1000'
          in: query
          name: pagesize
          schema:
            type: integer
      responses:
        '200':
          description: Ranked list of trending tickers with engagement scores
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/models.TrendingTickersListAPIResponse'
        '400':
          description: >-
            Bad request - missing or invalid source parameter, or invalid
            date/time format
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/bzhttp.Resp'
        '500':
          description: Internal server error
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/models.TrendingTickersListAPIResponse'
      security:
        - ApiKeyAuth: []
components:
  schemas:
    models.TrendingTickersListAPIResponse:
      properties:
        data:
          items:
            $ref: '#/components/schemas/models.TrendingTickersListData'
          type: array
        ok:
          example: true
          type: boolean
      type: object
    bzhttp.Resp:
      properties:
        data:
          additionalProperties: true
          type: object
        errors:
          items:
            $ref: '#/components/schemas/bzhttp.Error'
          type: array
        ok:
          type: boolean
      type: object
    models.TrendingTickersListData:
      properties:
        count:
          example: 1523
          type: integer
        pct_chg:
          example: 15
          type: integer
        security:
          $ref: '#/components/schemas/models.Security'
      type: object
    bzhttp.Error:
      properties:
        code:
          $ref: '#/components/schemas/bzhttp.ErrorCode'
        id:
          type: string
        value:
          type: string
      type: object
    models.Security:
      properties:
        exchange:
          example: NASDAQ
          type: string
        name:
          example: Apple Inc
          type: string
        ticker:
          example: AAPL
          type: string
      type: object
    bzhttp.ErrorCode:
      enum:
        - unsupported_message_type
        - database_query_error
        - json_unmarshaling_error
        - no_data_found
        - no_matching_endpoint
        - bad_request
        - db_error
        - internal_server_error
        - auth_failed
        - forbidden
        - failed_dependency
        - service_unavailable
        - upstream_api_error
      type: string
      x-enum-varnames:
        - ErrorUnsupportedMessageType
        - ErrorDBQueryError
        - ErrorJSONUnmarshaling
        - ErrorNoDataFound
        - ErrorNoMatchingEndpoint
        - ErrorBadRequest
        - ErrorDBError
        - ErrorInternalServerError
        - ErrorAuthFailed
        - ErrorForbidden
        - ErrorFailedDependency
        - ErrorServiceUnavailable
        - ErrorUpstreamAPIError
  securitySchemes:
    ApiKeyAuth:
      in: query
      name: token
      type: apiKey

````