Skip to main content
​
2026-02-20
Search v1
Include Audit ParameterAdded a new optional include_audit boolean parameter to the Search endpoint (/v1/search). When set to true, the response metadata will include an audit object containing the resolved queries that were actually executed, which is useful for debugging and understanding how the system interpreted your request.The audit object contains a queries array, where each entry shows the resolved filters, ranking parameters, and other settings used for that sub-query.Example Request:
{
    "include_audit": true,
    "search_mode": "smart",
    "query": {
        "text": "Can you summary the Q&A in the 2025 Q4 earnings call of Figma?"
    }
}
Example Response (metadata):
{
    "metadata": {
        "request_id": "47266b88-998a-4f90-84b7-f1d400d01652",
        "timestamp": "2026-02-21T21:42:55.205914+00:00",
        "audit": {
            "queries": [
                {
                    "auto_enrich_filters": false,
                    "filters": {
                        "document_type": {
                            "mode": "INCLUDE",
                            "values": [
                                {
                                    "type": "TRANSCRIPT",
                                    "subtypes": ["EARNINGS_CALL"]
                                }
                            ]
                        },
                        "reporting_entities": ["BA9E0C"],
                        "reporting_periods": [
                            {
                                "fiscal_year": 2025,
                                "fiscal_quarter": 4
                            }
                        ]
                    },
                    "max_chunks": 100,
                    "ranking_params": {
                        "source_boost": 1.0,
                        "freshness_boost": 1.0,
                        "reranker": {
                            "enabled": true
                        }
                    }
                }
            ]
        }
    }
}
See the Search Documents API reference for more details.
​
2026-02-16
Search v1Batch
Batch Search APIProcess large volumes of search requests asynchronously with 50% lower costs. Submit a .jsonl file containing multiple search queries, monitor progress, and download results when complete.New Endpoints:
  • Create a Batch Job (POST /v1/search/batches) - Get a batch_id and presigned_url for uploading your input file.
  • Upload Your Input File - Upload your .jsonl file to the presigned URL.
  • Get Batch Job Info (GET /v1/search/batches/{batch_id}) - Check job status and retrieve results when complete.
See the Batch Search API reference for more details, or follow the Batch Search how-to guide for a step-by-step walkthrough.
​
2026-02-16
Content v1
Bigdata Content APIIntroducing the Bigdata Content API (/contents/v1/), a new REST API for managing and querying content that you or your organization onboard to Bigdata. Use it to bring your own data into Bigdata and make it available for Search and Research Services.The API is organized around three areas:
  • Connectors: Create and manage ingestion sources (e.g. email inbox, SharePoint). Configure connectors to receive content and optionally share it across your organization.
  • Documents: Manage your uploaded documents. Get metadata, download the original file, or fetch the annotated (structured) version of your files.
  • Tags: Discover and use tags (e.g. sender/recipient for emails) to interact with your content.
See the Bigdata Content API for full documentation.
​
2026-02-13
Search v1
Document and Chunk Query FiltersAdded two new query filters to the Search and Co-mention endpoints (/v1/search, /v1/search/volume, /v1/search/co-mentions/entities, /v1/search/co-mentions/topics).
  • Document filter: Restrict the search to a list of specified documents. Use document IDs (e.g., from a previous search response) with mode (INCLUDE or EXCLUDE) and values (array of document IDs).
  • Chunk filter: Narrow the search to a particular section within a document. Use from and to (1-based chunk indices, inclusive) to expand the context around a previously retrieved chunk.
Example:
{
    "query": {
        "filters": {
            "document": {
                "mode": "INCLUDE",
                "values": ["3C54E042B2B19B244F57D3C6415439D1"]
            },
            "chunk": {
                "from": 3,
                "to": 7
            }
        }
    }
}
See the Search API reference for full details.
​
2026-02-11
Documents v1
Documents Endpoint UpdateUpdated the /v1/documents/{document_id} endpoint to support both public web content and premium documents.The endpoint now returns a URL along with a type field indicating how the document should be accessed:
  • For public web content, the response includes a direct link to the original publisher’s website.
  • For premium or licensed content, the response includes a pre-signed URL (valid for 24 hours) that can be used to download the document in JSON format.
Example:
GET /v1/documents/776769957735667D2F01F695EF4F1231
Example Response (public web content):
{
    "url": "https://www.example.com/news/article",
    "type": "web"
}
Example Response (premium content):
{
    "url": "https://documents.bigdata.com/v1/documents/776769957735667D2F01F695EF4F1231?signature=abc123...",
    "type": "json"
}
See the Fetch Document API reference for full details and usage guidelines.
​
2026-02-06
Search v1
Search Mode ParameterAdded a new optional search_mode parameter to the Search endpoint (/v1/search). This parameter determines how the search query is processed.Available modes:
  • fast (default): Runs a single query against the vector DB using the specified filters. Best for pre-processed queries where you control the filters.
  • smart: Analyzes the query text to automatically define advanced search filters and runs multiple sub-queries to ensure better coverage. Ideal for sending user questions directly without pre-processing. Has higher latency than fast mode.
Important: When using smart mode, only timestamp and source filters are allowed. Using any other filters will result in a 400 Bad Request error.Example:
{
    "search_mode": "smart",
    "query": {
        "text": "What's the CapEx of Alphabet in the 2026 fiscal year?"
    }
}
See the Search Documents API reference for more details.
​
2026-02-04
Workflows v1
Workflows API LaunchIntroducing the Workflows API for templated, reproducible research workflows.Key Features:
  • Templated Prompts with Jinja2 and parameterized inputs
  • Template Management (CRUD operations)
  • Community Templates to discover and clone
  • Research Plans for structured execution
  • Model Selection (base, pro, gemini, claude variants)
  • Content Filtering and Time Range Control
Endpoints:
  • POST /v1/workflow/execute - Execute a workflow
  • GET/POST /v1/workflow/templates - List/Create templates
  • GET/PUT/DELETE /v1/workflow/templates/{id} - Manage templates
  • GET /v1/workflow/templates/community - Browse community templates
  • POST /v1/workflow/templates/{id}/clone - Clone a template
See the Workflows API documentation.
​
2026-02-03
Content
Fetch Document EndpointAdded a new /documents/{document_id} endpoint that returns the full document in JSON format. The response includes a pre-signed URL, valid for 24 hours, which can be used to download the target document.Example:
GET /v1/documents/776769957735667D2F01F695EF4F1231
Example Response:
{
    "url": "https://documents.bigdata.com/v1/documents/776769957735667D2F01F695EF4F1231?signature=abc123..."
}
See the Fetch Document API reference for full details and usage guidelines.
​
2026-01-30
Search v1
Auto Enrich Filters ParameterAdded a new optional auto_enrich_filters parameter to the query object in all Search endpoints (/v1/search, /v1/search/volume, /v1/search/co-mentions/entities, /v1/search/co-mentions/topics).This advanced parameter controls automatic enrichment of filters using the query text:
  • true (default): The system automatically extracts and adds relevant filter values from the query text.
  • false: Disables automatic enrichment, useful when you have created a strict query with specific keywords and entity filters and you do not want any extra values added to those filters.
Example:
{
    "query": {
        "text": "Microsoft earnings",
        "filters": {
            "entity": {
                "any_of": ["228D42"]
            }
        },
        "max_chunks": 10,
        "auto_enrich_filters": false
    }
}
See the Search Documents API reference for more details.
​
2026-01-09
Structured Data
Pagination Added to Events Calendar APIPagination support has been added to the Events Calendar REST endpoint (/v1/events-calendar), making it easier to work with large sets of past and upcoming events and to build scalable, production-ready integrations. See the Events Calendar API reference for more details.
  • Enables efficient navigation of large event datasets through paginated responses.
  • Supports scalable client integrations by reducing payload size and request complexity.
  • Improves the ability to build responsive user interfaces and event-driven workflows.
​
2025-12-19
Search v1
Granular Category Filter ValuesThe category filter in the RESTful Search endpoint (/v1/search) and related endpoints now supports more granular category values, allowing customers to search by categories at a more precise level.In addition to the existing categories, the following new granular categories are now available:News Categories:
  • news_premium - Premium news sources
Research Categories:
  • research_academic_journals - Academic journal research
The original categories (expert_interviews, filings, my_files, news, podcasts, research, transcripts) continue to be supported for backward compatibility.Example:
{
    "query": {
        "text": "market analysis",
        "filters": {
            "category": {
                "mode": "INCLUDE",
                "values": [
                    "news_premium"
                ]
            }
        }
    }
}
See the Search Documents API reference for more details.
​
2025-12-15
Search v1Volume
Search Volume EndpointAdded a new /v1/search/volume endpoint that returns document and chunk volume statistics over time for a search query, aggregated by date with sentiment analysis. This endpoint uses the same request parameters as the /v1/search endpoint, except for ranking_params and max_chunks.This endpoint is valuable for several use cases:
  • Evaluate the product: Customers can see how many unique documents Bigdata has available for their particular query, which sets us apart from competitors.
  • Narrative/Thematic screeners: Users can create a query and see how the defined narrative evolves over time.
  • Query strategy: Users can check the coverage and plan how to create queries accordingly.
The response includes daily volume statistics (documents, chunks, and average sentiment) for each date in the time range, as well as aggregated totals across all dates.Efficient Usage: This endpoint consumes exactly 1 API Query Unit regardless of the time period queried, making it a very efficient way to visualize narrative evolution over time without extracting specific chunks of text.Example:
{
    "query": {
        "text": "Tariffs impact",
        "filters": {
            "timestamp": {
                "start": "2025-01-01T14:15:22Z",
                "end": "2025-12-15T14:15:22Z"
            }
        }
    }
}
Example Response:
{
    "results": {
        "volume": [
            {
                "date": "2025-01-01",
                "documents": 164,
                "chunks": 387,
                "sentiment": -0.15
            },
            {
                "date": "2025-01-02",
                "documents": 1363,
                "chunks": 3570,
                "sentiment": -0.16
            },
            ... // other dates
        ],
        "total": {
            "documents": 3440,
            "chunks": 8196,
            "sentiment": -0.18
        }
    },
    "metadata": {
        "request_id": "473d22ea-7753-41d8-825a-4a4c7696f8cb",
        "timestamp": "2025-12-15T17:34:34.181589+00:00"
    },
    "usage": {
        "api_query_units": 1.0
    }
}
See the Search Volume API reference for more details, or check out the Theme Volume Evolution how-to guide for a complete example with visualization.
​
2025-12-12
Structured Data
Sentiment API launch & Earnings Data EnhancementsAdded
  • Launched the Sentiment REST endpoint (/v1/entity-sentiment), enabling programmatic access to sentiment signals derived from news and content sources. See the Entity Sentiment API reference for more details.
Improved
  • Expanded Earnings Calendar API coverage, providing improved access to upcoming and historical earnings events across supported companies.
  • Improved structure, consistency, and completeness of Earnings Calendar API responses to support more reliable downstream integrations.
  • Enhanced data validation and response handling across select financial datasets to reduce inconsistencies.
  • Improved overall API reliability and performance for high-volume requests.
Fixed
  • Fixed issues where certain API responses could return incomplete or inconsistent data under specific conditions.
  • Addressed minor response formatting issues across select endpoints.
​
2025-12-04
Search v1
Search in Headlines, Body, or BothAdded a new optional search_in parameter to the keyword, entity, and topic filter objects in the RESTful Search endpoint (/v1/search). See the Search Documents API reference for more details.This parameter allows you to specify where to search for keywords, entities, or topics:
  • HEADLINE: Search only in document headlines
  • BODY: Search only in document body text
  • ALL: Search in both headlines and body text (default)
If the search_in parameter is not provided, it defaults to ALL, maintaining backward compatibility with existing API calls.Example:
{
    "query": {
        "text": "",
        "filters": {
            "keyword": {
                "search_in": "HEADLINE",
                "all_of": ["Snowflake"],
                "any_of": [],
                "none_of": []
            }
        },
        "ranking_params": {
            "source_boost": 10,
            "freshness_boost": 10
        },
        "max_chunks": 50
    }
}
​
2025-11-14
Search v1
Sentiment Filter with Custom RangesAdded a new ranges parameter to the sentiment filter in the RESTful Search endpoint (/v1/search). This parameter allows you to filter documents by custom sentiment score ranges, providing more precise control over sentiment filtering than the previous values parameter.The ranges parameter accepts an array of objects, each specifying a min and max sentiment score (ranging from -1.0 to 1.0). You can specify multiple ranges to capture different sentiment segments.Sunsetting: The values parameter (which accepted ["positive", "negative", "neutral"]) is now sunsetting. While it will continue to work for backward compatibility, we recommend migrating to the new ranges parameter for more precise sentiment filtering.Example:
{
    "query": {
        "text": "Solid state battery research",
        "filters": {
            "sentiment": {
                "ranges": [
                    {
                        "min": -1,
                        "max": -0.3
                    },
                    {
                        "min": 0.3,
                        "max": 1
                    }
                ]
            }
        },
        "ranking_params": {
            "source_boost": 10,
            "freshness_boost": 10
        },
        "max_chunks": 50
    }
}
See the Search Documents API reference for more details.
​
2025-11-11
Search v1
Tag Filter for Uploaded DocumentsAdded a new tag filter to the RESTful Search endpoint (/v1/search) that allows you to find uploaded documents with specific tags. This filter is particularly useful when working with private uploaded files or forwarded emails that have been tagged.The tag filter accepts an any_of parameter containing an array of tag strings. Documents matching any of the specified tags will be included in the search results.Example:
{
    "query": {
        "text": "stock",
        "filters": {
            "source": {
                "mode": "INCLUDE",
                "values": [
                    "000000",   // Private uploaded files
                    "9790B7"    // Private forwarded emails
                ]
            },
            "tag": {
                "any_of": ["Data Science Research"]
            }
        },
        "max_chunks": 10
    }
}
See the Search Documents API reference for more details.
​
2025-11-10
Search v1
Custom Reranker ThresholdAdded a new optional threshold parameter to the reranker object in the ranking_params of the RESTful Search endpoint (/v1/search). This parameter allows you to set a custom threshold to filter results by relevance score, improving precision and reducing noise.The threshold parameter accepts a float value ranging from 0.0 to 1.0. The default reranker uses a threshold of 0.2, but you can set a custom threshold to control result quality. Higher values return fewer, more relevant results.Example:
{
    "query": {
        "text": "Quantum computer pattern",
        "ranking_params": { 
            "source_boost": 10,
            "freshness_boost": 1,
            "reranker": {
                "enabled": true,
                "threshold": 0.8
            }
        }
    }
}
See the Search Documents API reference for more details.
​
2025-11-10
Search v1
Category FilterAdded a new category filter to the RESTful Search endpoint (/v1/search) that allows you to filter documents by category. This enables selecting a related set of sources without having to add a long list of source IDs.The category filter accepts a mode parameter (INCLUDE or EXCLUDE) and a values array containing one or more category names. The currently supported categories are:
  • expert_interviews
  • filings
  • my_files
  • news
  • podcasts
  • research
  • transcripts
Example:
{
    "query": {
        "text": "tariffs",
        "filters": {
            "category": {
                "mode": "INCLUDE",
                "values": [
                    "expert_interviews",
                    "news",
                    "research"
                ]
            }
        }
    }
}
See the Search Documents API reference for more details.
​
2025-10-03
Structured Data
Expanded API Coverage for Companies, Financials, and FundsThese new APIs give clients richer company fundamentals and the ability to screen & analyze funds with more precision:
  • Company Profile (/v1/company-profile) retrieving comprehensive company profile data.
  • Revenue Geographic Segments (/v1/company-revenue-geographic-segments) providing revenue data for a company broken down by geographic regions.
  • Revenue Product Segments (/v1/company-revenue-product-segments) delivering detailed revenue data for a company segmented by product lines or business units.
  • Stock & Funds Screener (/v1/company-screener) enabling advanced screening of stocks and funds.
  • Fund Holdings (/v1/holdings/funds/stocks) delivering institutional fund holdings and portfolio summary data.
See the Structured Data Introduction for more details.
​
2025-09-26
Structured Data
New Core Financial & Market Data EndpointsThis release introduces a set of core financial and market data APIs, including comprehensive company financial statements, trailing ratios, daily and intraday prices, price changes, and real‑time quotes.
  • Income Statement (/v1/income-statement) returning a company’s income statement data.
  • Cash Flow Statement (/v1/cash-flow-statement) providing a company’s cash flow statement data.
  • Daily Prices (/v1/price/daily) delivering end‑of‑day pricing data for equities.
  • Company Ratios TTM (/v1/company-ratios-ttm) returning trailing twelve‑month financial ratios for a company.
  • Intraday Prices (/v1/price/intraday) providing intraday (within‑day) pricing data for equities.
  • Price Changes (/v1/price/changes) delivering computed price change metrics.
  • Quote (/v1/quote) returning the latest real‑time or near‑real‑time quote for an equity.
See the Structured Data Introduction for more details.
​
2025-09-19
Structured Data
New Core Financial & Market Data EndpointsThis release introduces a set of core financial and market data APIs, including comprehensive company financial statements, trailing ratios, daily and intraday prices, price changes, and real‑time quotes.
  • Earnings Surprises (/v1/latest-surprise) returning actual earnings vs. consensus estimates along with surprise metrics.
  • Key Metrics TTM (/v1/key-metrics-ttm) providing key trailing twelve‑month performance metrics.
  • Balance Sheet (/v1/balance-sheet) delivering a company’s balance sheet data.
  • Analyst Ratings (/v1/analyst-ratings) returning aggregated analyst rating data.
  • Analayst Estimates (/v1/analyst-estimates) providing detailed analyst forecast estimates for metrics.
  • Events Calendar (/v1/events-calendar) delivering scheduled company and market events.
See the Structured Data Introduction for more details.