News

Market News

GET/v2/news/market

Returns market-wide financial news. Optionally filter by date range using from and to parameters.

Included in: Growth.

Authentication

Send your API key in the x-api-key header on every request to https://api.bavest.co. The samples read it from the BAVEST_API_KEY environment variable. Get an API key · Authentication guide

Parameters

Name	In	Type	Required	Description
limit	query	integer	no	Maximum number of articles to return (default 20, max 100) Default `20`
from	query	string (date)	no	Start date (YYYY-MM-DD)
to	query	string (date)	no	End date (YYYY-MM-DD)
cursor	query	string	no	Opaque cursor for cursor-based pagination. When provided, returns results after the cursor position. Takes precedence over offset.

Try it

GET /v2/news/market

API key

Sent only to api.bavest.co for this request; not stored.

Sign in to send Get an API keySends with the key above, or sign in to use your account's key. Each request counts as one API call.

curl 'https://api.bavest.co/v2/news/market' \
  -H "x-api-key: $BAVEST_API_KEY"

Samples read your key from BAVEST_API_KEY and follow the form.

Example response 200

{
  "data": [
    {
      "publishedDate": "2026-10-01T19:51:00",
      "title": "DOOR (OTC: LTCH) Resolves Final Legacy Matter, Completing Four-Year Turnaround of Its Financial Reporting and Legal Obligations",
      "site": "prnewswire.com",
      "text": "SEC settlement follows the filing of seven years of financial statements and resolution of four shareholder lawsuits; Company refocuses fully on profitability. ST. LOUIS, Oct. 1, 2026 /PRNewswire/ -- DOOR (OTC: LTCH), today announced that the Securities and Exchange Commission (the \"SEC\") has approved the Company's previously disclosed settlement, resolving the SEC's investigation.",
      "url": "https://www.prnewswire.com/news-releases/door-otc-ltch-resolves-final-legacy-matter-completing-four-year-turnaround-of-its-financial-reporting-and-legal-obligations-302896725.html"
    },
    {
      "publishedDate": "2026-10-01T19:43:15",
      "title": "Nike Q1: The Company Of The Past Is Gone",
      "site": "seekingalpha.com",
      "text": "Nike, Inc. remains unattractive despite a 76% five-year decline, still trading at 21x forward earnings. Q1 earnings revealed a 4% revenue decline, with significant weakness in Europe and Greater China; guidance was notably below consensus. Expense management improved margins, but increased 'demand creation' spending failed to stem revenue losses, highlighting execution and competitive challenges.",
      "url": "https://seekingalpha.com/article/4951482-nike-q1-the-company-of-the-past-is-gone"
    }
  ],
  "meta": {
    "page": 1,
    "pageSize": 20,
    "totalPages": 2794,
    "totalCount": 55862,
    "parameters": {
      "limit": "20"
    },
    "time": 34
  }
}

From the docs, not your data. Long lists are cut to 3 items.

Response 200

Successful response · application/json

dataarray of NewsArticle
- symbolstring | null
  Resolved ticker the article was matched to
  Example AAPL
- titlestring
  Article headline
  Example Apple Reports Record Q1 Revenue
- textstring
  Article body or summary text
- sitestring
  Publisher domain
  Example benzinga.com
- publishedDatestring (date-time)
  Publication date and time
- urlstring (uri)
  Article URL
metaResponseMeta
Response metadata for paginated endpoints. Offset pagination returns page/pageSize/totalPages/totalCount; cursor pagination returns pageSize/hasMore/nextCursor and totalCount only when known.
- timeinteger
  Server-side processing time in milliseconds
  Example 17
- parametersobject
  Echo of the request parameters the endpoint resolved
- pageinteger
  Current page number (offset pagination)
  Example 1
- pageSizeinteger
  Number of results per page
  Example 50
- totalPagesinteger
  Total number of pages (offset pagination)
  Example 2
- totalCountinteger
  Total number of results across all pages
  Example 100
- hasMoreboolean
  Whether more results follow (cursor pagination)
- nextCursorstring | null
  Cursor for the next page (cursor pagination), null on the last page

Errors

400Invalid request parameters. Returned when required query parameters are missing, have invalid types, or violate constraints (e.g., providing both symbol and isin when they are mutually exclusive).
401Missing or invalid API key.
404Resource not found.
429Rate limit exceeded. Retry after the `Retry-After` header interval.
500An unexpected error occurred on the server. If the issue persists, contact support with the X-Request-Id header value.
502Upstream data provider returned an error or is temporarily unavailable. Retry after a short delay.
504The request timed out waiting for a response from the upstream data provider. This may occur for complex queries or during peak load.
defaultAn unexpected error occurred on the server. If the issue persists, contact support with the X-Request-Id header value.