Legacy migration
Find current documentation for older Bavest guides and understand topics without a documented public v2 equivalent.
Bavest API v0 is deprecated. Older guide URLs now lead to current topic documentation or the migration notes below. A documentation redirect does not update API requests, parsers or SDKs.
For the unresolved topics below, no directly equivalent public v2 route is documented in the current published reference. This does not establish that the underlying service is discontinued. Confirm availability and integration requirements with Bavest before depending on a replacement.
ESG and emissions
The legacy Carbon Footprint, ESG Company Data, ESG Sustainability and standalone ESG Emissions guides described distinct datasets. No directly equivalent public v2 route is documented for those standalone endpoints. General company profiles or financial metrics are not an established replacement for emissions measurements, ESG scores or sustainability records.
Before migrating, identify the exact measures, units, reporting period and company identifiers your application needs. Ask Bavest to confirm their availability and delivery contract; do not infer an API path from an old endpoint name.
Standalone Sentiment
The old standalone Sentiment endpoint has no directly equivalent public v2 route documented in the current reference. A news feed or an analyst recommendation is a different resource and must not be treated as the same sentiment series.
Record whether you need article-level scores, company aggregates or a historical series, including the model, score scale and timestamps. Confirm those requirements with Bavest before changing the integration.
Python and Dart SDKs
The archived Python and Dart SDK guides do not establish that any package release supports the current v2 request or response contract. An installed package or a successful import alone does not demonstrate compatibility.
- Inventory the SDK methods your application calls and the API version each uses.
- Compare each method with the current REST reference: HTTP method, query parameters, authentication and response fields.
- Use a supported SDK version only after confirming its compatibility. Otherwise use your language's HTTP client with the documented v2 contract and test the response handling before release.
- Start with a current v2 request
- Authentication
- MCP for AI clients: a separate integration option; not a Python or Dart SDK compatibility claim
Market data and indices
The current v2 reference documents Real-Time Quote, OHLCV Candles and End-of-Day Price below. Compare their parameters, response fields and coverage with your older Quote, Candle, Stock Candles or EOD integration before migrating. The legacy Historical Price, index catalogue and Stock Revenue Product guides still have no directly equivalent public v2 route documented here. A security search does not replace an index catalogue or index constituents.
For prices, establish the asset class, exchanges, real-time or delayed status, historical depth, corporate-action adjustments and candle resolution you require. For indices, distinguish index identifiers from membership and constituent weights. Confirm the appropriate delivery contract with Bavest.
- Real-Time Quote
- OHLCV Candles
- End-of-Day Price
- Security Search: identifier lookup only; not an index or price-history replacement
Streaming
The old Websocket, Realtime Streaming and AWS Kinesis guides cover transports and subscription contracts separate from the published REST reference. This reference does not document a directly equivalent public v2 streaming route. That does not establish that streaming services are discontinued.
Do not reuse a legacy WebSocket URL or assume REST authentication, entitlements, topic names or event schemas apply to a stream. Confirm the supported transport, exchange coverage, subscription access, handshake and event contract with Bavest. MCP is an agent tool interface, not a market-event streaming replacement.
Legacy metrics and formulas
Older ETF Fundamentals and metric/formula guides describe legacy fields and calculations. Similar metric names alone do not establish identical formulas, periods, units or null handling in v2. The old ETF Profile formula pages concern risk calculations; they are not a complete definition of the current ETF Profile response.
- Equity Metrics: current fields and equity migration notes
- ETF Metrics: current ETF metric contract
- ETF Risk: current risk resource; no assertion of legacy formula parity
- Financials migration: choose periodic statements or the latest TTM snapshot
Reconcile each required field and calculation against current documentation and representative results before replacing production calculations. Ask Bavest for definitions that the published reference does not supply.
Reference lists
The old Stock Economics Calendar has no directly equivalent public v2 calendar route documented here; individual economic indicator series do not replace an events calendar. The archived Documents, Exchanges, Countries, Currencies, Resolutions, Sectors and Industries pages were shared lookup tables for older APIs. There is no documented public v2 replacement for those exact legacy lists. Do not assume old exchange suffixes, currency codes, sector labels or resolution values remain valid for every v2 route.
Use the parameters and enums on the specific current endpoint. Country lists for economic indicators or ETF exposure have their own scope and are not universal replacements. Use Security Search when you need to resolve a supported security identifier; verify the endpoint's accepted identifier before requesting data.
Next steps
When checking an unresolved legacy integration with Bavest, include the old guide name, required dataset, identifiers, frequency and fields. Confirm the published contract and account access before shipping a migration.
This page as Markdown: /docs/legacy-migration.md

