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

# Batch Get Sub-Sector timeseries

> Social sentiment score aggregated over the assets in a sub-sector. Each series is one sub-sector, keyed by its name.



## OpenAPI

````yaml api-reference/data-api/openapi.json GET /query/timeseries/sub-sector-asset-sentiment/{granularity}
openapi: 3.0.0
info:
  description: >-
    The Blockworks Data API is a unified, read-only REST interface to
    Blockworks' warehouse-modeled crypto dataset, powered by Messari's research
    and data infrastructure. It serves two kinds of models: tabular models,
    which return current, filterable, sortable rows for entities such as assets,
    networks, protocols, exchanges, stablecoins, and ETFs; and timeseries
    models, which return historical metric series at a chosen granularity for
    one or many entities. Every endpoint shares the same query grammar (column
    projection, per-column filters, sorting, and pagination) and returns the
    standard `{ "error": ..., "data": ... }` envelope. Authenticate by sending
    your API key in the `X-Blockworks-API-Key` header.
  title: Blockworks Data API
  version: 0.1.0
servers:
  - description: Blockworks API
    url: https://api.blockworks.com
security:
  - apiKey: []
tags:
  - description: 'Models documented under Acquisitions: Acquisition Deals (table).'
    name: Acquisitions
  - description: >-
      Models documented under Assets: Assets (table), Asset Marketcap
      (timeseries), Asset Price (timeseries), Asset Sharpe (timeseries), Asset
      Supply (timeseries), Asset Volatility (timeseries).
    name: Assets
  - description: >-
      Models documented under Blockchains: Blockchains (table), Blockchains
      (timeseries).
    name: Blockchains
  - description: >-
      Models documented under Derivatives: Perpetual Markets (table), Perpetual
      Markets (timeseries).
    name: Derivatives
  - description: >-
      Models documented under Digital Asset Treasuries: DAT Companies (table),
      DAT Company Assets (table), DAT Companies (timeseries), DAT Companies by
      Asset (timeseries).
    name: Digital Asset Treasuries
  - description: >-
      Models documented under ETFs: ETF Assets (table), ETF Providers (table),
      ETF Assets (timeseries), ETF Providers (timeseries).
    name: ETFs
  - description: >-
      Models documented under Exchanges: Exchange Country (timeseries), Exchange
      Region (timeseries), Exchange Type (timeseries), Exchanges (timeseries).
    name: Exchanges
  - description: >-
      Models documented under Funding Rounds: Funding Round Investors (table),
      Funding Rounds (table), Sector Fundraising (timeseries).
    name: Funding Rounds
  - description: >-
      Models documented under Funds & Investors: Fund Managers (table), Funds
      (table).
    name: Funds & Investors
  - description: >-
      Models documented under Launchpads: Launchpad Chains (table), Launchpads
      (table), Launchpads (timeseries), Launchpads by Chain (timeseries).
    name: Launchpads
  - description: >-
      Models documented under Lending Protocols: Lending Protocol Product
      Markets (table), Lending Protocol Products (table), Lending Protocols
      (table), Lending Protocols (timeseries), Lending Protocols by Product
      (timeseries), Lending Protocols by Product Market (timeseries).
    name: Lending Protocols
  - description: >-
      Models documented under Market Overview: Sector Marketdata (timeseries),
      Sub-Sector Marketdata (timeseries).
    name: Market Overview
  - description: 'Models documented under Markets: Market (BQEN) (timeseries).'
    name: Markets
  - description: >-
      Models documented under News & Research: News Feed (table), Research
      Reports (table), Topics (timeseries).
    name: News & Research
  - description: >-
      Models documented under Perp DEXes: Perp DEX Protocols (table), Perp DEX
      Protocols (timeseries).
    name: Perp DEXes
  - description: 'Models documented under Projects & Entities: Projects (timeseries).'
    name: Projects & Entities
  - description: >-
      Models documented under Protocol Revenue: Protocol Revenue (timeseries),
      Protocol Revenue by Product (timeseries).
    name: Protocol Revenue
  - description: >-
      Models documented under Social & Mindshare: Asset Group Sentiment
      (timeseries), Asset Investor Mentions (timeseries), Asset Mindshare
      (timeseries), Asset Sentiment (timeseries), Project Mindshare
      (timeseries), Sector Asset Mindshare (timeseries), Sector Asset Sentiment
      (timeseries), Sector Investor Mentions (timeseries), Sub-Sector Asset
      Mindshare (timeseries), Sub-Sector Asset Sentiment (timeseries).
    name: Social & Mindshare
  - description: >-
      Models documented under Spot DEXes: Spot DEX Protocol Chains (table), Spot
      DEX Protocols (table), Spot DEX Protocols (timeseries), Spot DEX Protocols
      by Chain (timeseries).
    name: Spot DEXes
  - description: >-
      Models documented under Stablecoins: Stablecoin Chains (table), Stablecoin
      Currencies (table), Stablecoin FX Pairs (table), Stablecoin Issuers
      (table), Stablecoin Products (table), Stablecoin Reserve Entities (table),
      Stablecoin FX (timeseries), Stablecoin Reserves (timeseries), Stablecoins
      by Chain (timeseries), Stablecoins by Currency (timeseries), Stablecoins
      by Issuer (timeseries), Stablecoins by Product (timeseries).
    name: Stablecoins
  - description: >-
      Models documented under TCG Platforms: TCG Platform Chains (table), TCG
      Platforms by Chain (timeseries).
    name: TCG Platforms
  - description: >-
      Discovery of the tabular models: one row per entity, with per-column
      filters, sorting and pagination.
    name: Tabular
  - description: >-
      Discovery of the timeseries models: one series per entity, as points at
      the granularities each model declares.
    name: Timeseries
  - description: >-
      Models documented under Token Transparency Framework: Token Transparency
      Filing Questions (table), Token Transparency Filing Schemas (table), Token
      Transparency Filings (table), Token Transparency Projects (table).
    name: Token Transparency Framework
  - description: >-
      Models documented under Tokenized Commodities: Tokenized Commodities
      (table), Tokenized Commodity Chains (table), Tokenized Commodity Issuers
      (table), Tokenized Commodity Products (table), Tokenized Commodities by
      Chain (timeseries), Tokenized Commodities by Commodity (timeseries),
      Tokenized Commodities by Issuer (timeseries), Tokenized Commodities by
      Product (timeseries).
    name: Tokenized Commodities
  - description: >-
      Models documented under Tokenized Equities: Tokenized Equities (table),
      Tokenized Equity Chains (table), Tokenized Equity Issuers (table),
      Tokenized Equity Products (table), Tokenized Equities by Chain
      (timeseries), Tokenized Equities by Equity (timeseries), Tokenized
      Equities by Issuer (timeseries), Tokenized Equities by Product
      (timeseries).
    name: Tokenized Equities
  - description: >-
      Models documented under Vaults: Vault Chains (table), Vault Curators
      (table), Vault Protocols (table), Vault Curators (timeseries), Vault
      Protocols (timeseries), Vaults by Chain (timeseries).
    name: Vaults
paths:
  /query/timeseries/sub-sector-asset-sentiment/{granularity}:
    get:
      tags:
        - Social & Mindshare
      summary: Batch Get Sub-Sector timeseries
      description: >-
        Social sentiment score aggregated over the assets in a sub-sector. Each
        series is one sub-sector, keyed by its name.
      operationId: getTimeseries_sub_sector_asset_sentiment
      parameters:
        - description: Data granularity.
          in: path
          name: granularity
          required: true
          schema:
            enum:
              - 1h
              - 6h
              - 1d
            type: string
        - description: >-
            Comma-separated Sub-Sectors values naming the series to return (up
            to 10). Omit it to get every Sub-Sector as a series in one response.
          in: query
          name: series
          schema:
            type: string
        - description: >-
            Time window, one of: to-date (ytd, qtd, mtd, dtd, htd); relative,
            <n> followed by m, h, d or w (30d, 12h, 4w; 1y and 1M are not
            accepted, use 365d, 52w, ytd or a calendar year); a calendar day
            (YYYY-MM-DD), month (YYYY-MM) or year (YYYY); or an RFC3339 instant,
            which runs from then to now. Mutually exclusive with start/end.
            Default: everything retained, up to now.
          in: query
          name: timeframe
          schema:
            type: string
        - description: >-
            Window start, inclusive (RFC3339, unix seconds, or YYYY-MM-DD).
            Default: unbounded.
          in: query
          name: start
          schema:
            type: string
        - description: >-
            Window end, exclusive (RFC3339, unix seconds, or YYYY-MM-DD).
            Default: now.
          in: query
          name: end
          schema:
            type: string
        - description: >-
            If true, return only the first and last point of the resolved time
            window instead of every point in it.
          in: query
          name: bounds
          schema:
            type: boolean
        - description: >-
            Comma-separated metric fields to return; defaults to every metric. A
            point always leads with its timestamp, and the values that follow
            are described by point_schema in catalog order regardless of the
            order requested here.
          in: query
          name: selections
          schema:
            items:
              enum:
                - score
              type: string
            type: array
        - description: >-
            Response format, overriding the Accept header: json (default), csv,
            or jsonl (NDJSON). csv and jsonl return the rows as a downloadable
            file.
          in: query
          name: acceptFormat
          schema:
            default: json
            enum:
              - json
              - csv
              - jsonl
            type: string
      responses:
        '200':
          content:
            application/json:
              example:
                data:
                  point_schema:
                    - description: Timestamp of the data point.
                      field: time
                      name: Time
                      time: true
                      type: time
                    - description: The asset sentiment score of the sub-sector.
                      field: score
                      name: Score
                      time: false
                      type: float64
                  series:
                    - key: <Sub-Sectors>
                      points:
                        - - 1704067200
                          - 123.45
                error: null
              schema:
                properties:
                  data:
                    $ref: '#/components/schemas/SubSectorAssetSentimentData'
                  error:
                    nullable: true
                    type: string
                required:
                  - data
                type: object
            application/x-ndjson:
              schema:
                description: JSON Lines (NDJSON); one JSON object per line.
                type: string
            text/csv:
              schema:
                description: CSV with a header row; one row per record.
                type: string
          description: Timeseries points for each series.
        '400':
          content:
            application/json:
              example:
                data: null
                error: 'too many series requested: 11 exceeds the maximum of 10'
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: >-
            The request is malformed: an empty, duplicated or too long series
            list (at most 10 keys), an unknown query parameter, an unrecognized
            timeframe (1y and 1M are not accepted; use 365d, 52w, ytd or a
            calendar year), timeframe combined with start or end, an unknown
            selections field, or an invalid bounds or acceptFormat value.
        '401':
          content:
            application/json:
              example:
                data: null
                error: this model requires authentication
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: No API key was sent and the model requires one.
        '403':
          content:
            application/json:
              example:
                data: null
                error: this model requires the "social_mindshare_unified" permission
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: >-
            The API key is not valid, or does not hold the
            "social_mindshare_unified" permission.
        '404':
          content:
            application/json:
              example:
                data: null
                error: >-
                  model "sub-sector-asset-sentiment" does not support
                  granularity "1w" (supported: 1h, 6h, 1d)
              schema:
                $ref: '#/components/schemas/ErrorResponse'
          description: >-
            The path names a model that does not exist ("no timeseries model
            ..."), or a granularity the model is not available at. An unknown
            series key is not a 404: it is returned with an empty points array.
components:
  schemas:
    SubSectorAssetSentimentData:
      properties:
        point_schema:
          items:
            properties:
              description:
                type: string
              field:
                type: string
              name:
                type: string
              time:
                type: boolean
              type:
                type: string
              unit:
                description: What the value is denominated in. Absent for a plain number.
                enum:
                  - usd
                  - btc
                  - sats
                  - eth
                  - gwei
                  - native-token
                  - percent
                  - count
                  - ratio
                type: string
            type: object
          type: array
        series:
          items:
            properties:
              key:
                type: string
              points:
                items:
                  description: >-
                    A unix timestamp (seconds) followed by the metric values, in
                    point_schema order.
                  items:
                    nullable: true
                    type: number
                  type: array
                type: array
            type: object
          type: array
      required:
        - point_schema
        - series
      type: object
    ErrorResponse:
      properties:
        data:
          description: Always null on an error.
          nullable: true
          type: object
        error:
          description: What went wrong, in one sentence.
          type: string
      required:
        - error
        - data
      type: object
  securitySchemes:
    apiKey:
      description: >-
        API key sent in the `X-Blockworks-API-Key` header; `x-messari-api-key`
        is accepted for existing integrations. The catalog endpoints and models
        on the public access tier need no key.
      in: header
      name: X-Blockworks-API-Key
      type: apiKey

````