← All integrations

Benzinga

15 operations0 webhooks

Benzinga plugin for Corsair

Supported operations

  • Get Consensus RatingsRead-only

    Get aggregated analyst consensus rating and price targets for one ticker (GET /api/v1/consensus-ratings)

  • Get Earnings StreamRead-only

    Get the WebSocket URL for the real-time earnings calendar stream (wss://api.benzinga.com/api/v2.1/calendar/earnings/stream); append token=<api key> to connect

  • List Conference CallsRead-only

    List conference call data (GET /api/v2.1/calendar/conference-calls, page/pagesize pagination)

  • List DividendsRead-only

    List dividends calendar data (GET /api/v2.2/calendar/dividends, page/pagesize pagination)

  • List EarningsRead-only

    List earnings calendar data (GET /api/v2.1/calendar/earnings, page/pagesize pagination)

  • List EconomicsRead-only

    List economic calendar data (GET /api/v2.1/calendar/economics, page/pagesize pagination)

  • List GuidanceRead-only

    List company guidance data (GET /api/v2.1/calendar/guidance, page/pagesize pagination)

  • List IposRead-only

    List IPO calendar data (GET /api/v2.1/calendar/ipos, page/pagesize pagination)

  • List RatingsRead-only

    List analyst ratings data (GET /api/v2.1/calendar/ratings, page/pagesize pagination)

  • List RemovedRead-only

    List removed calendar events by type and update time (GET /api/v2.1/calendar-removed/, page/pageSize pagination)

  • List SplitsRead-only

    List stock split data (GET /api/v2.1/calendar/splits, page/pagesize pagination)

FAQ

Install corsair and @corsair-dev/benzinga, add the Benzinga plugin, and connect with an API key. Then call methods like corsair.benzinga.api.calendar.getConsensusRatings() from your app. Corsair syncs data per tenant.

Yes. Benzinga requires an API key from your Benzinga account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit Benzinga, GitHub, Notion, Stripe, and the rest. Trigger Benzinga from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for benzinga plugin for corsair. Common builds include sync jobs, admin tooling, and agents that call Benzinga APIs from your backend. Local DB entities let you query synced Benzinga records without hitting the API on every read.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per Benzinga API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/benzinga in the open repo. When Benzinga ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your Benzinga data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store Benzinga data on your behalf.