Submit a ticket
Bridgewise Article
Home / Integration Guides / API Integrations / Identifier Search & Getting Started
BW
Bridgewise Developer Guide
Identifier Search & Getting Started
This guide explains how to authenticate, convert external identifiers (ISIN / Ticker-Exchange) to Bridgewise internal IDs, and start retrieving data.

◎ 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.

1) Access Token 2) Convert Identifiers 3) Use company_id / trading_item_id 4) Retrieve Data

1 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.

Tip
Use the generated access token in your authorization header for API requests.

2 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

ParameterExampleDescription
 identifier_type ticker_exchangeDefines the identifier format. Supported: ticker_exchange, ISIN.
 identifier TSLA-NASDAQThe global identifier you want to convert into a Bridgewise internal ID.

⌁ Response Breakdown

KeyExampleDescription
 company_name Tesla, Inc.Full company name
 company_id 27444752Bridgewise internal identifier for the company
 identifiers [object]Includes security IDs and trading item IDs (tickers/exchanges)

? Understanding Identifiers

The identifier-search response includes multiple identifier layers:

  • company_id — the internal Bridgewise identifier for the company.
  • security_id — identifies the security under the company (e.g., common stock, preferred, etc.).
  • trading_item_id — identifies a tradable listing (ticker + exchange). A company/security may have multiple listings.
Quick rule of thumb
Use company_id for most company-level endpoints. Use trading_item_id when you need an exchange-specific listing (price series, technicals, etc.).

✦ Example: Converting an ISIN

If your system uses ISINs, set identifier_type=ISIN.

Request:
curl -X 'GET' \ 'https://rest.bridgewise.com/identifier-search?identifier=US88160R1014&identifier_type=ISIN' \ -H 'accept: application/json'
Note
The response structure is the same as ticker_exchange — you will still get company_id, and may get multiple listings under trading_item_ids.

⇣ Example: Retrieving Company Data

Once you have a company_id, you can query company-level endpoints (metadata, fundamentals, recommendation, etc.).

Request:
curl -X 'GET' \ 'https://rest.bridgewise.com/companies/27444752?language=en-US' \ -H 'accept: application/json' \ -H 'authorization: Bearer <ACCESS_TOKEN>'
Why the language parameter matters
Many textual insights are localized. Use language (e.g., en-US, ja-JP) to receive the desired output language.

3 Step 3: Optional User Context (If Applicable)

Some flows may require passing a user_id or session context to support user personalization, tracking, or client-specific behavior.

Best practice
Use stable identifiers from your system (e.g., customer UUID). Avoid using emails or phone numbers if you don’t need them.

? Helpful Links

✓
You’re ready to integrate
Authenticate → Convert identifiers → Use company_id/trading_item_id → Retrieve data via Swagger-backed endpoints.
If you need help validating your requests or mapping identifiers, share a sample (identifier + identifier_type) and the endpoint you’re calling, and we’ll troubleshoot quickly.

Related Articles

Widget Integration Guide

Tenant Authentication Guideline

Bridget API Integration Guide

Bridget Widget Integration Guide

BridgeWise Support Escalation Guide