Dividends

Dividend Estimates

GET/v2/dividends/estimates

Bavest's per-share dividend forecast. Returns a per-share amount with lower and upper bounds, one annual estimate per date, newest first. Covers equities and ETFs. These are Bavest model forecasts, separate from the analyst consensus under Estimates.

Included in: Startup, Pro, Growth.

Authentication

Send your API key in the x-api-key header on every request to https://api.bavest.co. The samples read it from the BAVEST_API_KEY environment variable. Get an API key · Authentication guide

Parameters

Required: one of symbol, isin, for example symbol=AAPL.

Name	In	Type	Required	Description
symbol	query	string	one of symbol, isin	Stock ticker symbol (e.g., `AAPL`, `MSFT`, `GOOGL`). Provide exactly one of symbol or isin. Example `AAPL`
isin	query	string	one of symbol, isin	ISIN code (e.g., `US0378331005`). Provide exactly one of symbol or isin. Clear the symbol example before using an ISIN.

Try it

symbol query

Stock ticker symbol (e.g., `AAPL`, `MSFT`, `GOOGL`). Provide exactly one of symbol or isin.

isin query

ISIN code (e.g., `US0378331005`). Provide exactly one of symbol or isin. Clear the symbol example before using an ISIN.

GET /v2/dividends/estimates?symbol=AAPL

API key

Sent only to api.bavest.co for this request; not stored.

Sign in to send Get an API keySends with the key above, or sign in to use your account's key. Each request counts as one API call.

curl 'https://api.bavest.co/v2/dividends/estimates?symbol=AAPL' \
  -H "x-api-key: $BAVEST_API_KEY"

Samples read your key from BAVEST_API_KEY and follow the form.

Example response 200

{
  "data": {
    "meta": {
      "as_of": "2028-01-01",
      "years": 3
    },
    "estimates": [
      {
        "date": "2028-01-01",
        "fiscal_year": 2028,
        "fiscal_year_end": "2028-09-27",
        "expected_payment_year": 2028,
        "amount": 1.1377,
        "lower": 0.9179,
        "upper": 1.659,
        "is_estimate": true,
        "basis": "estimate",
        "source": "consensus_model",
        "payout_ratio": 0.1064,
        "currency": "USD",
        "model": {
          "amount": 1.058,
          "lower": 1.038,
          "upper": 1.081
        }
      },
      {
        "date": "2027-01-01",
        "fiscal_year": 2027,
        "fiscal_year_end": "2027-09-27",
        "expected_payment_year": 2027,
        "amount": 1.08,
        "lower": 0.9785,
        "upper": 1.3983,
        "is_estimate": true,
        "basis": "estimate",
        "source": "consensus_model",
        "payout_ratio": 0.1125,
        "currency": "USD",
        "model": {
          "amount": 1.053,
          "lower": 1.039,
          "upper": 1.069
        }
      }
    ]
  },
  "meta": {
    "parameters": {
      "symbol": "AAPL"
    },
    "time": 2262
  }
}

From the docs, not your data. Long lists are cut to 3 items.

Response 200

Successful response · application/json

dataDividendEstimatesResponse
Bavest's own per-share dividend forecast, newest first.
- metaobject
- estimatesarray of DividendEstimate
metaResponseMeta
Response envelope metadata. Always present on a 200: time is set by core/response.py on every successful response. Errors carry the same block, built by the same code, so a client parses one meta shape whether the call succeeded or failed.
- timeinteger
  Server-side processing time in milliseconds
  Example 17
- parametersobject
  Echo of the request parameters the endpoint resolved

Errors

400Invalid request parameters. Returned when required query parameters are missing, have invalid types, or violate constraints (e.g., providing both symbol and isin when they are mutually exclusive).
401Missing or invalid API key.
404Resource not found.
429Rate limit exceeded. Retry after the `Retry-After` header interval.
500An unexpected error occurred on the server. If the issue persists, contact support with the X-Request-Id header value.
502Upstream data provider returned an error or is temporarily unavailable. Retry after a short delay.
504The request timed out waiting for a response from the upstream data provider. This may occur for complex queries or during peak load.
defaultAn unexpected error occurred on the server. If the issue persists, contact support with the X-Request-Id header value.