Overview
The Bridgewise API provides a comprehensive interface to global financial data, covering a vast amount of publicly traded companies and ETFs worldwide. It delivers:
Raw numerical data
AI-driven recommendations
Insightful textual analyses, available in multiple native languages
Built on a RESTful architecture, the API ensures smooth integration and compatibility with modern development practices.
Getting Started
This guide will help you quickly onboard and begin using the Bridgewise API. The first step is obtaining Bridgewise internal identifiers, which act as the foundation for retrieving company, security, and trading-level data.
Step 1: Obtain an Access Token
To start integrating Bridgewise widgets, you’ll need an access token. Please follow the instructions in our Authentication Guide to generate your token.
Step 2: Obtain Bridgewise Internal Identifiers
All identifiers within the Bridgewise API are internal, but the system seamlessly supports conversion from globally recognized identifiers such as ISIN and Ticker-Exchange via identifier-search endpoint
This makes it easy to integrate the API with your existing data sources.
Example: Converting Tesla (Ticker-Exchange)
In this example, we submit the Tesla stock symbol to the identifier-search endpoint.
Request:
curl -X 'GET' \
'https://rest.bridgewise.com/identifier-search?identifier=TSLA-NASDAQ&identifier_type=ticker_exchange' \
-H 'accept: application/json'
Response:
{
"company_name": "Tesla, Inc.",
"company_id": 27444752,
"identifiers": [
{
"security_id": 108803914,
"security_name": "Common Stock",
"security_primary_flag": true,
"trading_item_ids": [
{
"trading_item_id": 108803915,
"trading_item_id_primary_flag": true,
"ticker_symbol": "TSLA",
"exchange_symbol": "NasdaqGS",
"exchange_name": "Nasdaq Global Select",
"exchange_id": 458,
"exchange_importance_level": 3
}
]
}
]
}
Request Parameters
Response Breakdown
Understanding Identifiers
When querying identifier-search, you may receive:
Company ID - Unique identifier for the company (used in most endpoints)
Security ID - Represents a security (mapped to an ISIN, not directly used)
Trading Item ID - Represents ticker-exchange pairs (used for ticker-level requests)
? Example (Tesla)
Tesla trades on 7 exchanges with 4 different ISINs.
All listings map to one company_id (27444752).
Within the company, there are multiple security_ids, each linked to an ISIN.
Each security has multiple trading_item_ids (Ticker-Exchange).
✅ The company_id is the primary identifier used in most endpoints.
✅ The trading_item_id is used for ticker-level queries.
❌ The security_id is not required in API requests.
Each endpoint in the Swagger documentation specifies which identifier is needed.
Example: Data Retrieval
After converting an external identifier, you can retrieve company details using the company_id.
Request:
curl -H 'Access Token: access-token' \
https://rest.bridgewise.com/companies/27444752
Response:
[
{
"language": "en-US",
"updated_at": "2025-09-18",
"company_id": 27444752,
"company_name": "Tesla, Inc.",
"company_name_short": "Tesla",
"website": "www.tesla.com",
"primary_ticker_symbol": "TSLA",
"primary_exchange_symbol": "NasdaqGS",
"region_id": 10359,
"region_name": "United States and Canada",
"incorporation_country_id": 213,
"incorporation_country_name": "United States",
"domicile_country_id": 213,
"domicile_country_name": "United States",
"gics_sector_id": 25,
"gics_sector_name": "Consumer Discretionary",
"gics_industry_group_id": 2510,
"gics_industry_group_name": "Automobiles & Components",
"gics_industry_id": 251020,
"gics_industry_name": "Automobiles",
"csa_industry_id": 5,
"csa_industry_name": "Automobiles",
"primary_currency_market_id": 160,
"primary_currency_market": "USD",
"primary_currency_financials_iso3": "USD",
"primary_security_id": 108803914,
"primary_security_name": "Common Stock",
"ipo_date": "2010-06-28",
"is_red_flagged": null,
}
]
Step 3: Include User Information in Requests
All API and widget endpoints require your integration to send a user_id.. This is mandatory and part of the commercial terms of using Bridgewise.
Why User ID is Required
Compliance with commercial agreements: ensures proper usage tracking per end-user.
Supports auditing and usage reporting for contractual obligations.
How to Include User ID
Add a user-id header in your request.
Example: Fundamental Analysis Request
curl 'https://rest.bridgewise.com/companies/27444752/fundamental-analysis' \
-H 'accept: application/json, text/plain, */*' \
-H 'authorization: Bearer <ACCESS_TOKEN>' \
-H 'user-id: <USER_ID>' \
Notes
The user-id is mandatory for API calls that provide personalized results or feed widgets.
Always ensure that user-id is unique per end-user and consistent across your integration.
Explore the Bridgewise API
You are now ready to navigate the Bridgewise API. Please note that we provide three separate Swagger documentations, each covering a different area of the platform:
For the complete reference, visit the Swagger documentation relevant to your use case. If you encounter issues, our technical support team is available at support@bridgewise.com.
Was this article helpful?
That’s Great!
Thank you for your feedback
Sorry! We couldn't be helpful
Thank you for your feedback
Feedback sent
We appreciate your effort and will try to fix the article