How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Benzinga

Benzinga Earnings Call Transcripts API

Real-time and historical conference-call transcripts, audio, AI-generated summaries, and speaker data, fetched by call ID or filtered lists.

Documentation Provider Profile APIs.io OpenAPI GitHub

Benzinga Earnings Call Transcripts API is one of 44 APIs that Benzinga publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Transcripts, Earnings Calls, and Audio. The published artifact set on APIs.io includes API documentation, an API reference, and an OpenAPI specification.

This API exposes 14 operations across 8 paths, organized into 5 resource areas, and defines 15 schemas. It is described by OpenAPI 3.0.0, at version 2.1.0.

Requests are made against a single base URL, https://api.benzinga.com.

14 operations 8 paths 15 schemas 3 DELETE5 GET1 POST5 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.0.0
API Version
2.1.0
Base URL
https://api.benzinga.com
Authentication
API Key
Terms of Service
View terms
Resource Areas
5

Authentication & Security 1

Benzinga Earnings Call Transcripts API declares 1 security scheme for authenticating requests. An API key is passed in the query as token (ApiKeyAuth).

Paths & Operations 14

Across 8 paths, the API surfaces 14 operations — 3 DELETE, 5 GET, 1 POST, 5 PUT. They span 5 resource areas: calls, participants, status, summaries, transcripts. Each is listed below with its method, path, parameters, and response codes.

calls 4
GET
/api/v1/transcripts/calls
Fetch all calls
get-conference-calls 11 params → 200400500
DELETE
/api/v1/transcripts/calls/{call_id}
Delete call by ID
delete-conference-call-by-id 1 param → 200400500
GET
/api/v1/transcripts/calls/{call_id}
Fetch call by ID
get-conference-call-by-id 6 params → 200400404500
PUT
/api/v1/transcripts/calls/{call_id}
Update call by ID
update-conference-call-by-id 1 param body → 200400500
participants 2
DELETE
/api/v1/transcripts/participants/{participant_id}
Delete participant by ID
delete-participant-by-id 1 param → 200400500
PUT
/api/v1/transcripts/participants/{participant_id}
Update participant by ID
update-participant-by-id 1 param body → 200400500
status 2
GET
/api/v1/transcripts/status
Query status view
query-status-view 5 params body → 200400500
POST
/api/v1/transcripts/status
Query status view
query-status-view 5 params body → 200400500
summaries 3
GET
/api/v1/transcripts/summaries
Fetch summaries
get-summaries 7 params → 200400500
GET
/api/v1/transcripts/summaries/{call_id}
Fetch summary by Call ID
get-summary-by-call-id 1 param → 200404500
PUT
/api/v1/transcripts/summaries/{call_id}
Update summary by Call ID
update-summary-by-call-id 1 param body → 200400500
transcripts 3
DELETE
/api/v1/transcripts/transcripts/{transcript_id}/segment/{segment_id}
Delete transcript segment by ID
delete-transcript-segments-by-id 2 params → 200400500
PUT
/api/v1/transcripts/transcripts/{transcript_id}/segment/{segment_id}
Update transcript segment by ID
update-transcript-segments-by-id 2 params body → 200400500
PUT
/api/v1/transcripts/transcripts/{transcript_id}/speaker
Update a speaker across a transcript
update-transcript-speaker 1 param body → 200400500

Schemas 15

The contract defines 15 schemas that model the data the API accepts and returns. The most detailed are domain.Calls (23 properties), domain.UpdateCallReq (11 properties), domain.Recordings (10 properties), domain.Summaries (10 properties). Each schema is shown below with its type and property counts.

api.QueryRequest
object
domain.Calls
object
23 properties
domain.Participants
object
8 properties
domain.Recordings
object
10 properties
domain.Summaries
object
10 properties
domain.TranscriptSegments
object
7 properties
domain.Transcripts
object
6 properties
domain.TranscriptsType
string
domain.UpdateCallReq
object
11 properties
domain.UpdateParticipantReq
object
5 properties
domain.UpdateSummaryReq
object
3 properties
domain.UpdateTranscriptSegmentsReq
object
4 properties
domain.UpdateTranscriptSpeakerReq
object
3 properties
pgtype.JSONB
object
2 properties
pgtype.Status
integer

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

benzinga-delivery-api-openapi.yml Raw ↑

Other APIs Benzinga publishes across the network.

Benzinga Newsfeed & Why Is It Moving API
AE Profile APIs.io
Benzinga Press Releases API
AE Profile APIs.io
Benzinga Ticker Trends API
AE Profile APIs.io
Benzinga Data Webhook Engine
AE Profile APIs.io
Benzinga WebSocket Streaming API
AE Profile APIs.io
Benzinga TCP Streaming Service
AE Profile APIs.io
Benzinga Analyst Insights API
AE Profile APIs.io
Benzinga Analyst Reports API
AE Profile APIs.io
Benzinga Block Trade API
AE Profile APIs.io
Benzinga Bulls Say Bears Say API
AE Profile APIs.io
Benzinga calls API
AE Profile APIs.io
Benzinga Channels API
AE Profile APIs.io
#Transcripts#Earnings Calls#Audio
← Back to B APIs
API Details
ID
benzinga:benzinga-earnings-call-transcripts-api
Base URL
https://api.benzinga.com
Docs
https://docs.benzinga.com/api-reference/delivery-api/overview
Provider
Benzinga
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=benzinga-earnings-call-transcripts-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/benzinga-earnings-call-transcripts-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

This is an independent, third-party profile of Benzinga Earnings Call Transcripts API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.