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

# List items in a category

> Returns companies and documents belonging to a category, sorted by publication date.

Results are a unified list of **companies** and **documents**, each identified by a `type` field. Use `limit` and `offset` for pagination.

The `meta` object varies by item type. For companies it includes `domain` and `logo`. For documents it includes `preview_image` and `document_type`.



## OpenAPI

````yaml GET /api/v1/categories/{category_slug}/items/
openapi: 3.0.3
info:
  title: Sacra API
  version: 1.0.0
  description: >-
    The Sacra API currently supports querying News, Documents, Companies and
    Categories that enable you to use Sacra research within your own
    application.


    ## **Getting started guide**


    To start using the APIs, you need to:


    - Only available to **Platforms** and **Funds** tier members. (See
    [here](https://sacra.com/pricing/))
        
    - You must use a valid API Key to send requests to the API endpoints. You
    can generate your API key in the Api Keys section of your [Organization
    Settings](https://sacra.com/orgs/settings/general/).
        
    - The API returns request responses in JSON format. When an API request
    returns an error, it is sent in the JSON response as an error key.
        

    ## Authentication


    The Sacra API uses Tokens for authentication.


    You can generate a Sacra API Key/Token in the Api Keys section of your
    [Organization Settings](https://sacra.com/orgs/settings/general/).


    You must include an API Key/Token in each request to the Sacra API with the
    **Authorization** request header.


    ### Authentication error response


    If a Token is missing, malformed, or invalid, you will receive an HTTP 401
    Unauthorized response code.


    ### **Need some help?**


    In case you have questions, we will eventually provide tutorials and a FAQ
    page. But for now you can check out the
    [#developers](https://discord.gg/mTswyV8gg3) channel in our community
    [Discord](https://discord.gg/mTswyV8gg3), there’s a good chance our
    community has an answer for you.


    ## Authorization


    | **Key** | **Value** |

    | --- | --- |

    | Authorization | Token {{API_KEY}} |
servers:
  - url: https://sacra.com
    description: Production
security: []
tags:
  - name: Companies
  - name: Categories
  - name: Events
  - name: News
  - name: Documents
  - name: Filings
  - name: Embeds
  - name: Metrics
  - name: Funding (Legacy)
paths:
  /api/v1/categories/{category_slug}/items/:
    get:
      tags:
        - Categories
      summary: List items in a category
      description: >-
        Returns companies and documents belonging to a category, sorted by
        publication date.


        Results are a unified list of **companies** and **documents**, each
        identified by a `type` field. Use `limit` and `offset` for pagination.


        The `meta` object varies by item type. For companies it includes
        `domain` and `logo`. For documents it includes `preview_image` and
        `document_type`.
      operationId: categories_items_retrieve
      parameters:
        - in: path
          name: category_slug
          schema:
            type: string
          description: Category slug to look up (e.g. `crypto`).
          required: true
        - in: query
          name: limit
          schema:
            type: integer
          description: Items per page, 1-100. Default 20.
        - in: query
          name: offset
          schema:
            type: integer
          description: Number of items to skip. Default 0.
      responses:
        '200':
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/CategoryItemsResponse'
              examples:
                CompanyAndDocumentItems:
                  value:
                    category:
                      id: 39
                      name: crypto
                      slug: crypto
                    items:
                      - type: company
                        id: 605
                        slug: chainalysis
                        title: Chainalysis
                        description: API and software for tracing crypto transactions
                        published_at: '2026-03-22T04:56:00Z'
                        meta:
                          domain: chainalysis.com
                          logo:
                            url: https://images.prismic.io/sacra/example.png
                            dimensions:
                              width: 398
                              height: 398
                      - type: document
                        id: 1778
                        slug: chainalysis-at-190m-arr
                        title: Chainalysis at $190M ARR
                        description: >-
                          Sacra estimates that Chainalysis hit $190M of annual
                          recurring revenue (ARR) in 2023.
                        published_at: '2024-08-30T00:00:00Z'
                        meta:
                          doc_type: market
                          pdf_url: >-
                            https://sacra-pdfs.s3.us-east-2.amazonaws.com/chainalysis-at-190m-arr.pdf
                    pagination:
                      limit: 20
                      offset: 0
                      total: 47
                      next_offset: 20
                  description: >-
                    Response truncated for brevity. Full response includes all
                    matching companies and documents.
          description: ''
        '400':
          content:
            text/plain:
              schema:
                type: string
                example: limit must be greater than 0.
          description: Invalid limit or offset.
        '404':
          content:
            text/plain:
              schema:
                type: string
                example: Category for requested slug not found.
          description: Category not found.
      security:
        - SacraAPIAuthentication: []
components:
  schemas:
    CategoryItemsResponse:
      type: object
      properties:
        category:
          $ref: '#/components/schemas/CategoryItemsCategory'
        items:
          type: array
          items:
            $ref: '#/components/schemas/CategoryItem'
        pagination:
          $ref: '#/components/schemas/CategoryItemsPagination'
      required:
        - category
        - items
        - pagination
    CategoryItemsCategory:
      type: object
      properties:
        id:
          type: integer
        name:
          type: string
        slug:
          type: string
      required:
        - id
        - name
        - slug
    CategoryItem:
      type: object
      properties:
        type:
          $ref: '#/components/schemas/TypeEnum'
        id:
          type: integer
        slug:
          type: string
        title:
          type: string
        description:
          type: string
          nullable: true
        published_at:
          type: string
          format: date-time
          nullable: true
        meta:
          type: object
          additionalProperties: {}
          description: >-
            Shape varies by `type`. For companies: `{domain, logo: {url,
            dimensions}}`. For documents: `{doc_type, pdf_url}`.
      required:
        - description
        - id
        - meta
        - published_at
        - slug
        - title
        - type
    CategoryItemsPagination:
      type: object
      properties:
        limit:
          type: integer
        offset:
          type: integer
        total:
          type: integer
        next_offset:
          type: integer
          nullable: true
      required:
        - limit
        - next_offset
        - offset
        - total
    TypeEnum:
      enum:
        - company
        - document
      type: string
      description: |-
        * `company` - company
        * `document` - document
  securitySchemes:
    SacraAPIAuthentication:
      type: apiKey
      in: header
      name: Authorization
      description: |-
        Authenticate using one of two formats:

        - **Organization/user token:** `Token <your-token>`
        - **Stytch JWT:** `Bearer <your-jwt>`

````