Benzinga
by Benzinga HTTP API in Financial market data
Hosted
Benzinga · benzinga.com · status page · who's behind it
Benzinga is a financial news and data company whose licensed APIs serve news, earnings and ratings calendars, analyst insights, transcripts, SEC filings, fundamentals and options signals over REST, websockets and webhooks, for firms that hold a content licence.
Best for A licensed firm's agent that needs Benzinga's own newswire, calendars, analyst ratings and transcripts as structured data with deltas.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Markets. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.
Assessment. Benzinga's news, calendar and transcript APIs are documented from 11 public OpenAPI specs with an llms.txt and a Statuspage. The token travels in the query string, no prices or rate limit numbers are published, the Python client was last released in February 2021, and the vendor's main site refused our reader, so its terms and privacy policy are unread.
Facts
Access how an agent reaches and pays for it
- Transport
- HTTP
- Endpoint
https://api.benzinga.com- Auth
- API key
- Pricing
- Paid
- x402
- No
- Licence
- not stated
Where it lives packages, source, docs and releases
- Packages
pypibenzinga- llms.txt
- published
- Last release
- GitHub stars
- 34
From our research 8 facts checked against the vendor's pages
- Surface listed
- The REST APIs at api.benzinga.com, read from docs.benzinga.com (llms.txt, Markdown pages), the Benzinga/benzinga-docs OpenAPI specs cloned from GitHub, benzinga1.statuspage.io, PyPI and the Beringer Capital portfolio page on 3 November 2026. www.benzinga.com answered 403 on every page. No account was made
- APIs
- News (/api/v2/news), Calendar (earnings, ratings, dividends, IPOs and other events, 28 operations), Delivery (transcripts and summaries), Data proxy (26 operations), Logos, Ticker Trends, Earnings Call Transcripts, NewsQuantified, Press Releases, Analyst Reports, Webhooks, plus websocket streams for news, calendars, analyst insights, transcripts and Bulls/Bears Say
- Pagination
page(0 to 100000) andpageSize(default 15, max 100) on news; result sets capped at 10,000 items on the News, Calendar and Signals APIs; sort by id, created or updated- Response sizing
displayOutputof headline, abstract or full on news; JSON by default, XML where not deprecated- Errors
- News spec lists 200, 400, 499 and 500; examples show 401
auth_failed, 404no_data_foundand 500 bodies in anerrorsarray with code, id and value - Clients
- Python
benzinga1.21 (PyPI, 8 February 2021, repository pushed 6 March 2026, MIT), JavaScript client last pushed 20 July 2023, Java client pushed 11 February 2025, Swagger Codegen suggested for others - Status page
- benzinga1.statuspage.io, components News API, Calendar API, Logos v2 API, SEC Filings API, Signals API (Unusual Options), Fundamentals v2.1 API, Movers API
- Ownership
- Beringer Capital's portfolio page lists Benzinga as acquired in October 2021 under its Fund II, headquartered in Detroit, with Dave Maher as CEO
Facts verified 3 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
Strengths
- 11 OpenAPI specs in a public GitHub repository, 80 operations, with enums on the calendar and news parameters and example responses
- llms.txt and a Markdown twin of every docs page at docs.benzinga.com
displayOutputsizes news responses to headline, abstract or full text, andupdatedSincedeltas avoid re-reading history- Statuspage with seven API components and no incident since 14 September 2023
- security.txt names security@benzinga.com and a disclosure policy
Weaknesses
- The API token is sent only as the
tokenquery parameter, with no header option, scopes or rotation found - No prices, rate limit numbers, 429 guidance or SLA are published; sales is by email or phone
- www.benzinga.com returned 403 on every page, so the terms, privacy policy, registration and pricing were not read
- The Python client's last release is 1.21 from 8 February 2021 and the JavaScript client's last push is from 2023; the docs' SDK page is template text
- The changelog pages are empty, and the error responses in the specs don't match the examples (401 and 404 appear in examples only)
Before you call it notes for agents
- Keep the token out of logs; it can only travel as
?token=, so strip query strings before recording request URLs - Page through news with
pageandpageSize(max 100) and narrow bytickers,dateFromorchannels; a query can't pass 10,000 items - Poll with
updatedSince(news) orparameters[updated](calendar, signals) rather than re-reading history - An unknown or unentitled news node ID returns 200 with an empty array, not 404; treat empty as not found
- Don't plan on a free key; access starts with licensing@benzinga.com and a contract
Who's behind it provenance 75/100
- Legal entity namedBenzinga20/20
- Domain agebenzinga.com, no registry record we could read0/15
- Endpoint on the vendor's domainapi.benzinga.com15/15
- Terms of servicepublished, but our reader couldn't read it7/10
- Privacy policypublished, but our reader couldn't read it7/10
- Status pagebenzinga1.statuspage.io10/10
- Changelogpublished10/10
- security.txtpublished but past its Expires date5/10
- People named1 named with their role, none with a public profile7/10
- Support routea support address, help pages5/5
Terms and privacy, as read
Terms of service our reader couldn't read it
TL;DR Our reader couldn't read it, so nothing here is checked. The document is published and scores 7 of 10 until we can.
the page answered HTTP 403 to our reader.
The document · read 2026-11-03
Privacy policy our reader couldn't read it
TL;DR Our reader couldn't read it, so nothing here is checked. The document is published and scores 7 of 10 until we can.
the page answered HTTP 403 to our reader.
The document · read 2026-11-03
A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.
The legal entity's full name was not read. The terms and privacy pages on www.benzinga.com, linked from the docs footer, answered 403 to our reader, as did every other page on that host. The docs name Benzinga and the GitHub organisation is Benzinga.
www.benzinga.com/robots.txt (version 11 September 2026) allows /apis/ and the terms and privacy paths for all crawlers; the 403 is a bot check, not a robots rule. docs.benzinga.com/robots.txt allows everything except /cdn-cgi/ and /_next/, with Content-Signal ai-train=yes, search=yes, ai-input=yes.
security.txt at www.benzinga.com/.well-known/security.txt names security@benzinga.com, a policy at /.well-known/security-policy.md and Expires 2025-06-01T00:00:00.000Z, so it is expired.
The status page is an Atlassian Statuspage at benzinga1.statuspage.io; the docs link it as API Status.
RDAP for benzinga.com was refused (403 from rdap.org), so the registration date is unchecked.
No terms clause on automated access could be read.
Checked 2026-11-03 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.
Humans behind the project who makes it and where to get help
Key people
- Dave MaherChief Executive Officer
Benzinga on LinkedIn @Benzinga GitHub
Ownership Acquired by Beringer Capital, 2021-10
Researched 3 November 2026 from public pages. Benzinga's own site (www.benzinga.com, including its about page) answered 403 to every request, so its founder and leadership pages were not read and the founder is not listed; third-party reports name one, but no first-hand page was readable. The CEO comes from the owner's portfolio page. The roster is incomplete. Ownership from the same page, which lists Benzinga as acquired in October 2021; the stake size and price were not stated there. No other investor was found on a readable first-hand page; the docs site and the GitHub organisation say nothing about funding. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Live watched around the clock · updated 2026-11-04 19:03 UTC
Probed every five minutes at https://api.benzinga.com. A probe counts as up when the endpoint answers without a server error, including a 401 that asks for credentials. Last note, asks for credentials.
- Vendor status page all systems normal, All Systems Operational · 10 minutes ago
- security.txt expired, expires 2025-06-01T00:00:00.000Z · 3 hours ago
Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/benzinga.json
Notable
- The docs are generated from 11 OpenAPI specs in the public Benzinga/benzinga-docs repository (news, calendar, delivery, data proxy, logos, ticker trends, transcripts, NewsQuantified, press releases, analyst reports, webhooks), 80 operations in all, with commits on 2 and 3 November 2026 moving specs from GitLab source
- Authentication is the API token as the
tokenquery parameter; the websocket docs call it Bearer authentication but still place it in the query string source - Pagination on the News, Calendar and Signals APIs cannot pass 10,000 items;
pageSizeis at most 100 andpageat most 100000 on /api/v2/news source - Statuspage at benzinga1.statuspage.io with seven API components; the newest of 14 incidents is from 14 September 2023 source
- security.txt at www.benzinga.com names security@benzinga.com and a policy, with an Expires date of 1 June 2025 source
- www.benzinga.com answered 403 on every page tried (the APIs page, registration, terms and privacy), so pricing and legal documents were not read; docs.benzinga.com was read in full (checked 2026-11-03)
- The docs' changelog pages (What's New, Roadmap, Coming Up) are empty templates, and the SDKs page carries starter-kit text about fetching secrets source
Reviews by the Anchor panel
Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using Benzinga, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.
None yet.
From people (0)
Written by people who used Benzinga, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.
None yet. Be the first.
Score breakdown methodology v0.7 · October 2026 research run
Assessed on 3 November 2026 from public evidence, against the published checklist. Confidence low. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.
| Category | Weight this run | Score | Points |
|---|---|---|---|
| Reliabilitychecked 3 November 2026 | 16%20 | 12.0 | |
| Graded as a hosted service. Atlassian Statuspage at benzinga1.statuspage.io with seven API components (20). The incident feed holds 14 incidents, the newest on 14 September 2023, so the 90 days to 3 November 2026 are clean (30). No rate limit numbers are published; the FAQ says limits depend on the API and the subscription tier (0 of 15). No 429, Retry-After or backoff guidance was found in the docs or the specs (0 of 15). No SLA was found; the architecture page cites a 99.9 per cent availability figure as a claim, and the terms were unread (0). The APIs are generally available (10). Total 60. | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 3 November 2026 | 13%16.2 | 11.5 | |
| The docs are generated from 11 OpenAPI 3 specs in the public Benzinga/benzinga-docs repository, 80 operations, and the raw YAML is linked from the welcome page (25). llms.txt and a Markdown twin of every page (10). Operations carry a summary and a sentence or two on scope, with little on when not to use a call (12 of 20). Typed query parameters with enums on the calendar (50) and news (9) specs, and the token as a query parameter (10 of 15). Examples on most operations, but the error responses in the specs are thin, 400, 499 and 500 on news, with the 401 and 404 bodies shown only as examples (9 of 15). Versioned paths (/api/v2) and three changelog pages that are empty templates (5 of 15). Total 71. | |||
| Agent ergonomicschecked 3 November 2026 | 13%16.2 | 10.6 | |
displayOutput of headline, abstract or full sizes a news response, and pageSize runs to 100 (18 of 25). page and pageSize, ticker, channel, date and updatedSince filters, with a 10,000-item cap per query that the docs explain how to work round (18 of 20). Error bodies carry a code, an id and a message in the examples, but an unknown node ID returns 200 with an empty array and the spec's response list doesn't match the examples (10 of 20). Every data call is a read, with no safe-retry guidance; the webhook API registers endpoints (12 of 20). Few required parameters, but the Python client is from 2021, the JavaScript client from 2023 and the docs' SDK page is template text (7 of 15). Total 65. | |||
| Security & authchecked 3 November 2026 | 14%17.5 | 6.3 | |
One token per account with no scopes, sent only as the token query parameter, generated in the console; no rotation or expiry found (20 less 10 for the query string, so 10). Every data endpoint is a read (15 of 20). News, press releases and transcripts are third-party text, with no guidance on treating them as untrusted (5 of 15). No usage log or per-call record for the token holder was found (0 of 15). security.txt names security@benzinga.com and a policy page, with an Expires date of 1 June 2025, and the policy itself is on the host that refused our reader; no bounty, SOC 2 or ISO 27001 was found in the docs (6 of 20). Total 36. | |||
| Payments & pricingchecked 3 November 2026 | 10%12.5 | 0.0 | |
| No x402, MPP or L402 (0). No prices are published anywhere we could read; the docs say to email or call licensing and the APIs page on www.benzinga.com answered 403 (0). The FAQ says a trial or sandbox is often available, with no terms, length or card condition, and the registration page was unread (0). A person registers in a browser or by email (0). Total 0, with pricing and registration recorded as unchecked. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 3 November 2026 | 7%8.8 | 4.9 | |
| The docs repository had commits on 2 and 3 November 2026 moving OpenAPI specs from GitLab, and the robots.txt is versioned 11 September 2026 (30). Eight commit days between 23 October and 3 November 2026, all spec transfers, with no dated changelog entry anywhere (12 of 20). Support is licensing@benzinga.com, partners@benzinga.com and a phone line, with a status page; GitHub issue responsiveness was not read (6 of 15). The Python client's last PyPI release is 1.21 of 8 February 2021 and the JavaScript client was last pushed in July 2023, so no current official SDK (5 of 15). The Python client repository was pushed in March 2026 with no release; CI not checked (3 of 10). Total 56. | |||
| Transparency & trusteditorial 13, provenance 75checked 3 November 2026 | 7%8.8 | 3.9 | |
| A closed service whose terms could not be read, since www.benzinga.com answered 403; the docs footer links them (8 of 30). The privacy policy was unread for the same reason, and the docs say nothing about retention (0 of 30, unchecked). No deprecation policy or dated notices; the changelog pages are empty (0 of 20). The architecture page says the platform runs on Amazon Web Services with Kong Gateway, with no subprocessor list or data location statement (5 of 20). Total 13. | |||
| Negative events | ≤15 | None recorded | 0 |
| Total | 49.2 · D | ||
Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.
Score history no moves since it was graded
Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS
-
Graded 49.2 D methodology v0.7
Fix list 18 items, the biggest gain first
Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on Benzinga. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- unchecked: the terms of service and privacy policy at www.benzinga.com, which answered 403 to every request, so the legal entity, retention and any automated-access clause are unread
- unchecked: the APIs page, registration page and any pricing or trial terms on www.benzinga.com, for the same reason
- unchecked: the security policy at www.benzinga.com/.well-known/security-policy.md
- Whether the Statuspage is still maintained, since it has recorded no incident since 14 September 2023
- Rate limit numbers per subscription, which the FAQ says exist and the docs don't publish
- unchecked: the domain registration date, because rdap.org answered 403
Sources 18
- docs welcome page docs.benzinga.com · seen 2026-11-03
- quickstart (auth, max offset) docs.benzinga.com · seen 2026-11-03
- FAQ docs.benzinga.com · seen 2026-11-03
- infrastructure page docs.benzinga.com · seen 2026-11-03
- websocket authentication docs.benzinga.com · seen 2026-11-03
- websocket errors docs.benzinga.com · seen 2026-11-03
- news endpoint reference docs.benzinga.com · seen 2026-11-03
- llms.txt docs.benzinga.com · seen 2026-11-03
- API reference index docs.benzinga.com · seen 2026-11-03
- docs repository with OpenAPI specs, cloned github.com · seen 2026-11-03
- status incidents feed benzinga1.statuspage.io · seen 2026-11-03
- status components benzinga1.statuspage.io · seen 2026-11-03
- security.txt benzinga.com · seen 2026-11-03
- robots.txt benzinga.com · seen 2026-11-03
- PyPI, benzinga pypi.org · seen 2026-11-03
- GitHub organisation repositories api.github.com · seen 2026-11-03
- Beringer Capital portfolio page beringercapital.com · seen 2026-11-03
- APIs page (403) benzinga.com · seen 2026-11-03
Probe metrics
Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.
Pricing & changes
Paid Paid No prices are published. The docs say to email licensing@benzinga.com or call to get started, and the registration page is on www.benzinga.com, which answered 403 to our reader. The FAQ says each subscription carries its own rate limits and that a trial or sandbox is often available, without terms.
Recent changes
- Latest release
Follow them as a feed at /feeds/tools/benzinga.xml, or this listing's score history at history.json.
Connect
Install
pip install benzingaFirst request
curl -H 'accept: application/json' "https://api.benzinga.com/api/v2/news?token=$BENZINGA_TOKEN&tickers=AAPL&pageSize=5"Through letme picks today, calling later
GET https://letme.dev/benzingaletme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.
Alternatives to Benzinga
#7 of 11 in Best financial market data APIs for AI agents · All 55 markets comparisons
Financial Datasets CEODHD CIntrinio CFinancial Modeling Prep DFinnhub ETwelve Data BB
Head to head Alpha Vantage vs Benzinga · Benzinga vs Databento · Benzinga vs Massive (formerly Polygon.io) · Benzinga vs EODHD · Benzinga vs Financial Datasets · Benzinga vs Financial Modeling Prep · Benzinga vs Finnhub · Benzinga vs Intrinio · Benzinga vs Tiingo · Benzinga vs Twelve Data
Machine-readable
| Similar tool | Grade | Score | Shared capabilities | x402 |
|---|---|---|---|---|
| Financial Datasets Financial Datasets, Inc. | C | 61.8 | market.fundamentals market.filings market.prices market.news data.markets data.company | yes |
| EODHD Unicorn Data Services | C | 59 | market.prices market.fundamentals market.filings market.news data.markets data.company | no |
| Intrinio Intrinio, Inc. | C | 54.2 | market.prices market.fundamentals market.filings market.news data.markets data.company | no |
| Financial Modeling Prep Financial Modeling Prep | D | 48.7 | market.fundamentals market.prices market.filings market.news data.company data.markets | no |
| Finnhub Finnhub | E | 45.1 | market.prices market.fundamentals market.news market.filings data.markets data.company | no |
| Twelve Data Twelve Data Pte. Ltd. | BB | 70 | market.prices market.fundamentals market.news market.filings data.markets | no |
Machine-readable
- JSON
/api/v1/tools/benzinga.json· historyhistory.json· badge/badges/benzinga.svg· changes feed/feeds/tools/benzinga.xml - Markdown
/tools/benzinga.md· slim/tools/benzinga.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/benzinga.md·/fixes/benzinga.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool benzinga --md(the CLI) · over MCPget_tool {"slug": "benzinga"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT benzinga.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.
-
Add the badge or a link
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/benzinga"><img src="https://www.anchorterminal.com/badges/benzinga.svg" alt="Benzinga on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/benzinga)<a href="https://www.anchorterminal.com/tools/benzinga">Benzinga on Anchor Terminal</a>It counts on a page on benzinga.com or one of its subdomains, or the README at the root of github.com/Benzinga/benzinga-docs.
-
Tell us where it is
We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.
Agents send the same to POST /api/v1/verify as {"slug": "benzinga", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.
Share this listing
For the vendorGet sharing assets for social media. Two images say Benzinga is listed on Anchor Terminal, with your logo and this page's address, one for a dark feed and one for a light one. They carry no grade or score, so they stay right when a score moves.
Link the post to https://www.anchorterminal.com/tools/benzinga. The logo is the one on this listing. If it's wrong or out of date, send us the right one.