Stock Events

Stock Events

Use the Stock Events API

The Stock Events API is a Pro feature for automating data in your Stock Events account from your own tools. It is designed for account automation, not as a general market-data or symbol-search API.

Write requests modify the same watchlists, symbols, and transactions that you see in Stock Events.

What you can do with the API

  • List, create, retrieve, and update watchlists.
  • List, add, update, and remove symbols in a watchlist.
  • List, create, retrieve, update, and delete transactions.
  • Read calculated Holdings and Dividends views.

How to create an API key

An active Stock Events Pro subscription is required to create and use API keys.

  1. Sign in to the Stock Events web app.
  2. Open your Profile.
  3. Select Settings.
  4. Under Account, select Data.
  5. Select API Keys.
  6. Select Create API key.
  7. Enter a descriptive Name, then select Create.
  8. Select Copy API key and store the key securely before closing the dialog.

The complete API key is shown only once. After you close the dialog, the API Keys screen shows its name, prefix, creation date, and last-used date instead of the complete key.

If your Pro subscription becomes inactive, your keys remain attached to your account, but API requests return 403 Forbidden until Pro access is active again.

Make your first request

The API base URL is https://stockevents.app/api/v1. Send your API key as a bearer token in the Authorization header.

curl -H "Authorization: Bearer $STOCK_EVENTS_API_KEY" \
  https://stockevents.app/api/v1/watchlists

This request returns your watchlists and their IDs. You can use a watchlist ID with the watchlist-specific symbol, Holdings, and Dividends endpoints.

For request fields, response structures, optional parameters, and all available endpoints, use these resources:

Keep your API key secure

Treat an API key like a password. Do not commit it to source control, expose it in public client code, or send it in a query parameter or request body.

API keys authenticate the account automation API without separate permissions for each key. Only use them with tools you trust.

If a key is exposed, return to API Keys, select Revoke API key, then confirm Revoke. The key stops working immediately and cannot be reactivated. Create a replacement key if needed.

Common errors

  • 401 Unauthorized: The API key is missing, invalid, or revoked.
  • 403 Forbidden: The account does not currently have active Pro access.