Finnhub.io icon

Finnhub.io

Consume Finnhub.io API

Stock → Stock Lobbying

AI-generated

Overview

This node interacts with the Finnhub.io API to retrieve stock lobbying data for a specified stock symbol within a given date range. It is useful for users who want to analyze lobbying activities related to specific stocks, which can provide insights into potential market influences or regulatory impacts. For example, a financial analyst might use this node to track lobbying efforts for a particular company over a quarter to assess external factors affecting stock performance.

Use Case Examples

  1. Retrieve lobbying data for Apple Inc. (AAPL) from 2023-01-01 to 2023-03-31 to analyze recent lobbying activities.
  2. Monitor lobbying activities for Tesla (TSLA) over the past month to understand potential regulatory influences.

Properties

Name Meaning
Premium Access Toggle to use premium Finnhub endpoints based on the user's credential.
Symbol The stock symbol for which lobbying data is requested.
From Start date for the lobbying data in YYYY-MM-DD format.
To End date for the lobbying data in YYYY-MM-DD format.
Request Options Additional request settings such as batching, SSL certificate handling, proxy configuration, and timeout settings.

Output

JSON

  • symbol - The stock symbol queried.
  • from - The start date of the lobbying data range.
  • to - The end date of the lobbying data range.
  • lobbyingData - Array of lobbying records related to the stock symbol within the specified date range.

Dependencies

  • Finnhub.io API
  • An API key credential for Finnhub.io

Troubleshooting

  • Ensure the stock symbol is valid and correctly formatted; invalid symbols may result in errors or empty responses.
  • Verify date formats are correct (YYYY-MM-DD) and that the 'From' date is not after the 'To' date.
  • Check API key permissions, especially if using premium endpoints, to avoid authorization errors.
  • If SSL errors occur, consider enabling the 'Ignore SSL Issues' option, but be aware of security risks.
  • Use batching options to manage rate limits and avoid request throttling errors.

Links

Discussion