# Company Subsidiaries Database > The subsidiary database holds information on subsidiaries of all publicly listed companies on US stock exchanges, with data extracted from Exhibit 21 of SEC filings. Find subsidiaries by ticker, CIK or name of the parent company, in historical data dating back to 2003. Convert Exhibit 21 files to JSON format. Ideal for comprehensive research and analysis with over 100,000 subsidiary lists available. Source: https://sec-api.io/docs/subsidiary-api The Subsidiary API provides access to a database of all current and historical subsidiaries belonging to publicly listed companies on US stock exchanges, from 2003 to present. The dataset, compiled from Exhibit 21 attached to SEC filings such as 10-K, 10-Q, S-1, or 20-F, is cleaned and converted to a JSON format, and provides the subsidiary names and jurisdictions along with associated metadata of the parent company. Data sample · Subsidiaries | Filed at | Ticker | Company | Subsidiary | Jurisdiction | CIK | Accession no. | | --- | --- | --- | --- | --- | --- | --- | | 2026-07-29 | MSFT | MICROSOFT CORP | Microsoft Ireland Research Unlimited Company | Ireland | 789019 | 0001193125-26-323660 | | 2026-07-29 | MSFT | MICROSOFT CORP | Microsoft Global Finance Unlimited Company | Ireland | 789019 | 0001193125-26-323660 | | 2026-07-29 | MSFT | MICROSOFT CORP | Microsoft Ireland Operations Limited | Ireland | 789019 | 0001193125-26-323660 | | 2026-07-29 | MSFT | MICROSOFT CORP | Microsoft Online, Inc. | United States | 789019 | 0001193125-26-323660 | | 2026-07-29 | MSFT | MICROSOFT CORP | LinkedIn Corporation | United States | 789019 | 0001193125-26-323660 | | 2026-07-29 | MSFT | MICROSOFT CORP | LinkedIn Ireland Unlimited Company | Ireland | 789019 | 0001193125-26-323660 | | 2026-07-29 | MSFT | MICROSOFT CORP | Activision Blizzard, Inc. | United States | 789019 | 0001193125-26-323660 | | 2026-07-29 | MSFT | MICROSOFT CORP | Activision Publishing, Inc. | United States | 789019 | 0001193125-26-323660 | | 2026-07-15 | NKE | NIKE, Inc. | Converse Inc. | Delaware | 320187 | 0000320187-26-000088 | | 2026-07-15 | NKE | NIKE, Inc. | NIKE Commercial (China) Co., Ltd. | China | 320187 | 0000320187-26-000088 | | 2026-07-15 | NKE | NIKE, Inc. | NIKE de Mexico, S. de R.L. de C.V. | Mexico | 320187 | 0000320187-26-000088 | | 2026-07-15 | NKE | NIKE, Inc. | NIKE Canada Corp. | Canada | 320187 | 0000320187-26-000088 | | 2026-07-15 | NKE | NIKE, Inc. | NIKE Europe Holding B.V. | Netherlands | 320187 | 0000320187-26-000088 | | 2026-07-15 | NKE | NIKE, Inc. | NIKE Global Trading B.V. | Netherlands | 320187 | 0000320187-26-000088 | | 2026-07-15 | NKE | NIKE, Inc. | NIKE Japan Group LLC | Japan | 320187 | 0000320187-26-000088 | | 2026-07-15 | NKE | NIKE, Inc. | NIKE Korea LLC | Korea | 320187 | 0000320187-26-000088 | | 2026-07-15 | NKE | NIKE, Inc. | NIKE Retail B.V. | Netherlands | 320187 | 0000320187-26-000088 | | 2026-07-15 | NKE | NIKE, Inc. | NIKE Retail Services, Inc. | Oregon | 320187 | 0000320187-26-000088 | | 2026-07-15 | NKE | NIKE, Inc. | NIKE Sport (China) Co., Ltd. | China | 320187 | 0000320187-26-000088 | | 2026-07-15 | NKE | NIKE, Inc. | NIKE Trading Company B.V. | Netherlands | 320187 | 0000320187-26-000088 | | 2026-02-25 | NVDA | NVIDIA CORP | Mellanox Technologies, Ltd | Israel | 1045810 | 0001045810-26-000021 | | 2026-02-25 | NVDA | NVIDIA CORP | NVIDIA International, Inc. | Delaware, U.S. | 1045810 | 0001045810-26-000021 | | 2026-02-25 | NVDA | NVIDIA CORP | NVIDIA Singapore Pte Ltd | Singapore | 1045810 | 0001045810-26-000021 | | 2026-02-11 | MA | Mastercard Inc | Global Mastercard Holdings LP | United Kingdom | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard A&M Investment Holdings, LLC | Delaware | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard AP Financing Pte. Ltd. | Singapore | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard Asia/Pacific Pte. Ltd. | Singapore | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard/Europay U.K. Limited | United Kingdom | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard Europe SA | Belgium | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard Europe Services Limited | United Kingdom | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard Financing Solutions LLC | Delaware | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard Holdings LP | United Kingdom | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard International Incorporated | Delaware | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard Middle East Africa FZ-LLC | United Arab Emirates | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard Payment Gateway Services Limited | United Kingdom | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard Payment Gateway Services Group Limited | United Kingdom | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard Singapore Holding Pte. Ltd. | Singapore | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard Technologies, LLC | Delaware | 1141391 | 0001141391-26-000013 | | 2026-02-11 | MA | Mastercard Inc | Mastercard US Holdings LLC | Delaware | 1141391 | 0001141391-26-000013 | | 2026-02-05 | AMZN | AMAZON COM INC | Amazon.com Services LLC | Delaware | 1018724 | 0001018724-26-000004 | | 2026-02-05 | AMZN | AMAZON COM INC | Amazon.com Sales, Inc. | Delaware | 1018724 | 0001018724-26-000004 | | 2026-02-05 | AMZN | AMAZON COM INC | Amazon Data Services, Inc. | Delaware | 1018724 | 0001018724-26-000004 | | 2026-02-05 | AMZN | AMAZON COM INC | Amazon Web Services, Inc. | Delaware | 1018724 | 0001018724-26-000004 | | 2026-02-05 | AMZN | AMAZON COM INC | Amazon Technologies, Inc. | Nevada | 1018724 | 0001018724-26-000004 | | 2026-02-05 | AMZN | AMAZON COM INC | Amazon.com NV Investment Holdings LLC | Nevada | 1018724 | 0001018724-26-000004 | | 2026-02-05 | AMZN | AMAZON COM INC | Amazon US Services LLC | Delaware | 1018724 | 0001018724-26-000004 | | 2026-02-05 | AMZN | AMAZON COM INC | A100 ROW, Inc. | Delaware | 1018724 | 0001018724-26-000004 | | 2026-02-05 | AMZN | AMAZON COM INC | Day One Insurance, Inc. | Arizona | 1018724 | 0001018724-26-000004 | | 2026-01-28 | META | Meta Platforms, Inc. | Facebook Holdings, LLC | Delaware | 1326801 | 0001628280-26-003942 | | 2026-01-28 | META | Meta Platforms, Inc. | Facebook Procurement, LLC | Delaware | 1326801 | 0001628280-26-003942 | | 2026-01-28 | META | Meta Platforms, Inc. | FCL Tech Limited | Ireland | 1326801 | 0001628280-26-003942 | | 2026-01-28 | META | Meta Platforms, Inc. | Instagram, LLC | Delaware | 1326801 | 0001628280-26-003942 | | 2026-01-28 | META | Meta Platforms, Inc. | Meta Payments Inc. | Florida | 1326801 | 0001628280-26-003942 | | 2026-01-28 | META | Meta Platforms, Inc. | Meta Platforms Ireland Limited | Ireland | 1326801 | 0001628280-26-003942 | | 2026-01-28 | META | Meta Platforms, Inc. | Siculus LLC | Delaware | 1326801 | 0001628280-26-003942 | | 2026-01-28 | META | Meta Platforms, Inc. | Sidecat LLC | Delaware | 1326801 | 0001628280-26-003942 | | 2026-01-28 | META | Meta Platforms, Inc. | WhatsApp LLC | Delaware | 1326801 | 0001628280-26-003942 | | 2026-01-23 | NFLX | NETFLIX INC | Netflix International B.V. | The Netherlands | 1065280 | 0001065280-26-000034 | | 2026-01-23 | NFLX | NETFLIX INC | Netflix Studios, LLC | United States | 1065280 | 0001065280-26-000034 | | 2026-01-23 | NFLX | NETFLIX INC | Netflix México S. de R.L. de C.V. | Mexico | 1065280 | 0001065280-26-000034 | | 2026-01-23 | NFLX | NETFLIX INC | Netflix Pte. Ltd. | Singapore | 1065280 | 0001065280-26-000034 | | 2026-01-23 | NFLX | NETFLIX INC | Netflix Services France S.A.S. | France | 1065280 | 0001065280-26-000034 | | 2026-01-23 | NFLX | NETFLIX INC | Netflix Services UK Limited | United Kingdom | 1065280 | 0001065280-26-000034 | | 2026-01-23 | NFLX | NETFLIX INC | Netflix Services Germany GmbH | Germany | 1065280 | 0001065280-26-000034 | | 2026-01-23 | NFLX | NETFLIX INC | Netflix Worldwide Entertainment, LLC | United States | 1065280 | 0001065280-26-000034 | | 2025-11-06 | V | VISA INC. | Visa Europe Limited | United Kingdom | 1403161 | 0001403161-25-000089 | | 2025-11-06 | V | VISA INC. | Visa International Service Association | Delaware | 1403161 | 0001403161-25-000089 | | 2025-11-06 | V | VISA INC. | Visa U.S.A. Inc. | Delaware | 1403161 | 0001403161-25-000089 | | 2025-11-06 | V | VISA INC. | Visa Worldwide Pte. Limited | Singapore | 1403161 | 0001403161-25-000089 | | 2025-10-31 | AAPL | Apple Inc. | Apple Asia Limited | Hong Kong | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple Asia LLC | Delaware, U.S. | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple Canada Inc. | Canada | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple Computer Trading (Shanghai) Co., Ltd. | China | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple Distribution International Limited | Ireland | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple India Private Limited | India | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple Insurance Company, Inc. | Arizona, U.S. | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple Japan, Inc. | Japan | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple Korea Limited | South Korea | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple Operations International Limited | Ireland | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple Operations Limited | Ireland | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple Operations Mexico, S.A. de C.V. | Mexico | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple Pty Limited | Australia | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple Services Pte. Ltd. | Singapore | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple South Asia (Thailand) Limited | Thailand | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple South Asia Pte. Ltd. | Singapore | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Apple Vietnam Limited Liability Company | Vietnam | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | Braeburn Capital, Inc. | Nevada, U.S. | 320193 | 0000320193-25-000079 | | 2025-10-31 | AAPL | Apple Inc. | iTunes K.K. | Japan | 320193 | 0000320193-25-000079 | | 2025-07-30 | MSFT | MICROSOFT CORP | Microsoft Ireland Research Unlimited Company | Ireland | 789019 | 0000950170-25-100235 | | 2025-07-30 | MSFT | MICROSOFT CORP | Microsoft Global Finance Unlimited Company | Ireland | 789019 | 0000950170-25-100235 | | 2025-07-30 | MSFT | MICROSOFT CORP | Microsoft Ireland Operations Limited | Ireland | 789019 | 0000950170-25-100235 | | 2025-07-30 | MSFT | MICROSOFT CORP | Microsoft Online, Inc. | United States | 789019 | 0000950170-25-100235 | | 2025-07-30 | MSFT | MICROSOFT CORP | LinkedIn Corporation | United States | 789019 | 0000950170-25-100235 | | 2025-07-30 | MSFT | MICROSOFT CORP | LinkedIn Ireland Unlimited Company | Ireland | 789019 | 0000950170-25-100235 | | 2025-07-30 | MSFT | MICROSOFT CORP | Activision Blizzard, Inc. | United States | 789019 | 0000950170-25-100235 | | 2025-07-30 | MSFT | MICROSOFT CORP | Activision Publishing, Inc. | United States | 789019 | 0000950170-25-100235 | ## Searching the Subsidiary Database The Subsidiary API serves data in JSON format, incorporating subsidiary names and jurisdictions along with associated metadata. This metadata includes the date/time of the parent company's subsidiary disclosure, the accession number of the primary filing that the Exhibit 21 subsidiary list is attached to, as well as the CIK, ticker, and company name of the parent company. The subsidiary database is searchable by various criteria, such as ticker, CIK, or the name of the parent company, subsidiary name, subsidiary jurisdiction, or a specific date range. Newly disclosed subsidiaries are added to the database in real-time as soon as new EDGAR filings with Exhibit 21 are published. The subsidiary database maintains all historically reported subsidiaries of their parent companies, dating back to 2003. For instance, querying the database using ticker "MSFT" would return all subsidiaries Microsoft reported since 2003. This provision allows you to conduct a thorough analysis of historical subsidiary data changes. ## Converting Exhibit 21 Files to JSON The Subsidiary API also enables the extraction of subsidiary information from a specific Exhibit 21 file and provides the data in JSON format. To do this, simply send a POST request with the filing's accession number, for example, `accessionNo:"0000950170-23-001409"`. The API will then return a JSON-formatted list of the subsidiaries disclosed in the exhibit. The accession number can be obtained from the URL of the exhibit or the corresponding EDGAR filing. ## Data Quantity & Accuracy Approximately 7,000 new lists of subsidiaries are reported every year, and the entire dataset encompasses over 100,000 lists of subsidiaries, dating back to 2003. While we utilize state-of-the-art machine learning algorithms to extract and standardize the data, inaccuracies may occur due to the non-standardized nature of the Exhibit 21 files. However, the error rate is minimal, affecting less than 0.1% (or 1 in 900) of the extracted lists of subsidiaries. Dataset size: 100,000+ lists of subsidiaries; all subsidiaries reported in Exhibit 21 since 2003. Data update frequency: Newly disclosed subsidiaries are added to the database in real-time as soon as new EDGAR filings with Exhibit 21 are published. Survivorship bias free: Yes. The database includes subsidiary information from all companies since 2003, including those that have gone out of business, merged, been acquired, went private, or delisted and stopped filing with the SEC for any other reason. ## API Endpoint To search and retrieve current and historical subsidiaries of publicly listed companies, send an HTTP `POST` request with the search query as a JSON payload to the following API endpoint: https://api.sec-api.io/subsidiaries Supported HTTP methods: `POST` Request and response content type: `JSON` ### Authentication To authenticate your API requests, use the API key available in your [user profile](https://sec-api.io/login). You can utilize your API key in one of two ways. Choose the method that best fits your implementation: - **Authorization Header:** Include your API key as an `Authorization` header in your `POST` requests. For instance, before sending a `POST` request to `https://api.sec-api.io/subsidiaries`, ensure the header is set as follows: `Authorization: YOUR_API_KEY`. - **Query Parameter:** Alternatively, append your API key directly to the URL as a query parameter. For example, when making `POST` requests, use the URL `https://api.sec-api.io/subsidiaries?token=YOUR_API_KEY` instead of the base endpoint. ## Request Parameters The Subsidiary API is designed to provide structured data in response to POST requests made with a JSON payload. This section describes the structure of the requests to the Subsidiary API and the specific parameters you should include in your request. The JSON payload you send in your POST request contains your search query, which should include the following parameters: **Request parameters:** - `query` (string) - Your search query. Boolean operators (AND, OR, NOT), range queries, wildcards (*) and nested conditions are fully supported. The query is written in Lucene syntax. More [information on Lucene is available here](https://sec-api.io/resources/lucene-query-syntax-overview). Example queries: `"ticker:MSFT"` returns a list of all subsidiaries of Microsoft disclosed since 2003. `"subsidiaries.jurisdiction:China OR subsidiaries.jurisdiction:PRC"` lists all subsidiaries of Chinese companies disclosed since 2003. `"cik:(37996 1318605)"` returns all subsidiaries of Ford (CIK 37996) and Tesla (CIK 1318605). - `from` (integer) - The start position of your search in the result universe. `from` is similar to an index of an array. Increase `from` in order to paginate through the results. For example, set `from` to 50 to get the next 50 matches. Default: 0. - `size` (integer) - The number of lists of subsidiaries to be returned in one response. Default: 50. Max: 50. - `sort` (array) - An array of sort definitions. Each array item defines the sort order of the result. Default:`[{ "filedAt": { "order": "desc" } }]` ### Request Examples Below are examples of JSON payloads demonstrating the structure of your POST request: Find all subsidiaries of Tesla (ticker: TSLA) reported in Exhibit 21 since 2003. ```json { "query": "ticker:TSLA", "from": "0", "size": "50", "sort": [{"filedAt":{"order":"desc"}}] } ``` List all subsidiaries of all companies reported in Exhibit 21 in 2020. Increment the `from` parameter to paginate through the results. ```json { "query": "filedAt:[2020-01-01 TO 2020-12-31]", "from": "0", "size": "50", "sort": [{"filedAt":{"order":"desc"}}] } ``` ## Response Structure **Response type:** JSON The API response represents a JSON object with two properties: `total` (object) and `data` (array). The `total.value` property indicates the total number of lists of subsidiaries matching your search query. The `data` array holds up to 50 lists of subsidiaries. An array item is an object and represents the following elements: - `id` (string) - System-internal unique identifier of the list of subsidiaries. - `accessionNo` (string) - Accession number of the EDGAR filing Exhibit 21 is attached to, e.g. `0001946140-22-000002`. - `filedAt` (date) - Date on which the list of subsidiaries was disclosed, e.g.`2022-10-12T17:29:52-04:00`. - `cik` (string) - The CIK of the parent company, e.g. `742118`. - `ticker` (string) - Ticker symbol of the parent company, e.g. `TSLA`. - `companyName` (string) - Name of the parent company, e.g. `Tesla, Inc.`. - `subsidiaries` (array) - List of subsidiaries of the parent company. Each item in the list is an object with the following properties: - `name` (string) - Name of the subsidiary, e.g. `Allegheny Solar 1, LLC`. - `jurisdiction` (string) - Jurisdiction of the subsidiary, e.g. `Delaware`. ### Response Example JSON ```json { "total": { "value": 24, "relation": "eq" }, "data": [ { "id": "6838a63b29128e116bde65c885282667", "accessionNo": "0000950170-23-001409", "filedAt": "2023-01-30T21:29:15-05:00", "cik": "1318605", "ticker": "TSLA", "companyName": "Tesla, Inc.", "subsidiaries": [ { "name": "Alabama Service LLC", "jurisdiction": "Delaware" } { "name": "Alset Warehouse GmbH", "jurisdiction": "Germany" }, { "name": "BT Connolly Storage, LLC", "jurisdiction": "Texas" }, { "name": "Fotovoltaica GI 4, S. de R.L. de C.V.", "jurisdiction": "Mexico" }, // ... more subsidiaries { "name": "Grohmann Engineering Trading (Shanghai) Co. Ltd.", "jurisdiction": "China" }, { "name": "Kansas Repair LLC", "jurisdiction": "California" }, { "name": "Roadster Finland Oy", "jurisdiction": "Finland" }, { "name": "SA VPP Holding Trust", "jurisdiction": "Australia" }, { "name": "SA VPP Project Trust", "jurisdiction": "Australia" }, { "name": "Sierra Solar Power (Hong Kong) Limited", "jurisdiction": "Hong Kong" }, { "name": "Tesla Automobile Sales and Service (Guangzhou) Co., Ltd.", "jurisdiction": "China" }, { "name": "Tesla (Beijing) New Energy R&D Co., Ltd.", "jurisdiction": "China" }, { "name": "Tesla Belgium BV", "jurisdiction": "Belgium" }, { "name": "Tesla Canada Finance ULC", "jurisdiction": "Canada" }, { "name": "Tesla Canada GP Inc.", "jurisdiction": "Canada" }, { "name": "Tesla Canada LP", "jurisdiction": "Canada" }, { "name": "Tesla Charging, LLC", "jurisdiction": "Delaware" }, { "name": "Tesla Construction (Shanghai) Co., Ltd.", "jurisdiction": "China" }, { "name": "Tesla Czech Republic s.r.o.", "jurisdiction": "Czech Republic" }, { "name": "Tesla Energia Macau Limitada", "jurisdiction": "Macau" }, { "name": "Tesla Energy d.o.o.", "jurisdiction": "Slovenia" }, { "name": "Tesla Energy Operations, Inc.", "jurisdiction": "Delaware" }, { "name": "Tesla Finance LLC", "jurisdiction": "Delaware" }, { "name": "Tesla Financial Leasing (China) Co., Ltd.", "jurisdiction": "China" }, { "name": "Tesla Financial Services GmbH", "jurisdiction": "Germany" }, { "name": "Tesla Financial Services Holdings B.V.", "jurisdiction": "Netherlands" }, { "name": "Tesla Financial Services Limited", "jurisdiction": "United Kingdom" }, { "name": "Tesla France S.à r.l.", "jurisdiction": "France" }, { "name": "Tesla Germany GmbH", "jurisdiction": "Germany" }, { "name": "Tesla General Insurance, Inc.", "jurisdiction": "Arizona" }, { "name": "Tesla Greece Single Member P.C.", "jurisdiction": "Greece" }, { "name": "Tesla Hrvatska d.o.o.", "jurisdiction": "Croatia" }, { "name": "Tesla Hungary Kft.", "jurisdiction": "Hungary" }, { "name": "Tesla India Motors and Energy Private Limited", "jurisdiction": "India" }, { "name": "Tesla Insurance Brokers Co., Ltd.", "jurisdiction": "China" }, { "name": "Tesla Insurance Holdings, LLC", "jurisdiction": "Delaware" }, { "name": "Tesla Insurance, Inc.", "jurisdiction": "Delaware" }, { "name": "Tesla Insurance Ltd.", "jurisdiction": "Malta" }, { "name": "Tesla Insurance Company", "jurisdiction": "California" }, { "name": "Tesla Insurance Services, Inc.", "jurisdiction": "California" }, { "name": "Tesla Insurance Services of Texas, Inc.", "jurisdiction": "Texas" }, { "name": "Tesla International B.V.", "jurisdiction": "Netherlands" }, { "name": "Tesla Investments LLC", "jurisdiction": "Delaware" }, { "name": "Tesla Italy S.r.l.", "jurisdiction": "Italy" }, { "name": "Tesla Jordan Car Trading LLC", "jurisdiction": "Jordan" }, { "name": "Tesla Korea Limited", "jurisdiction": "Republic of Korea" }, { "name": "Tesla Lease Trust", "jurisdiction": "Delaware" }, { "name": "Tesla LLC", "jurisdiction": "Delaware" }, { "name": "Tesla Manufacturing Brandenburg SE", "jurisdiction": "Germany" }, { "name": "Tesla Michigan, Inc.", "jurisdiction": "Michigan" }, { "name": "Tesla Mississippi LLC", "jurisdiction": "Delaware" }, { "name": "Tesla Motors Australia, Pty Ltd", "jurisdiction": "Australia" }, { "name": "Tesla Motors Austria GmbH", "jurisdiction": "Austria" }, { "name": "Tesla Motors (Beijing) Co., Ltd.", "jurisdiction": "China" }, { "name": "Tesla Motors Canada ULC", "jurisdiction": "Canada" }, { "name": "Tesla Motors Coöperatief U.A.", "jurisdiction": "Netherlands" }, { "name": "Tesla Motors Denmark ApS", "jurisdiction": "Denmark" }, { "name": "Tesla Motors FL, Inc.", "jurisdiction": "Florida" }, { "name": "Tesla Motors HK Limited", "jurisdiction": "Hong Kong" }, { "name": "Tesla Motors Iceland ehf.", "jurisdiction": "Iceland" }, { "name": "Tesla Motors Ireland Limited", "jurisdiction": "Ireland" }, { "name": "Tesla Motors Israel Ltd.", "jurisdiction": "Israel" }, { "name": "Tesla Motors Japan GK", "jurisdiction": "Japan" }, { "name": "Tesla Motors Limited", "jurisdiction": "United Kingdom" }, { "name": "Tesla Motors Luxembourg S.à r.l.", "jurisdiction": "Luxembourg" }, { "name": "Tesla Motors MA, Inc.", "jurisdiction": "Massachusetts" }, { "name": "Tesla Motors Netherlands B.V.", "jurisdiction": "Netherlands" }, { "name": "Tesla Motors New York LLC", "jurisdiction": "New York" }, { "name": "Tesla Motors NL LLC", "jurisdiction": "Delaware" }, { "name": "Tesla Motors NV, Inc.", "jurisdiction": "Nevada" }, { "name": "Tesla Motors PA, Inc.", "jurisdiction": "Pennsylvania" }, { "name": "Tesla Motors Romania S.R.L.", "jurisdiction": "Romania" }, { "name": "Tesla Motors Sales and Service LLC", "jurisdiction": "Turkey" }, { "name": "Tesla Motors Singapore Holdings Pte. Ltd.", "jurisdiction": "Singapore" }, { "name": "Tesla Motors Singapore Private Limited", "jurisdiction": "Singapore" }, { "name": "Tesla Motors Stichting", "jurisdiction": "Netherlands" }, { "name": "Tesla Motors Taiwan Limited", "jurisdiction": "Taiwan" }, { "name": "Tesla Motors TN, Inc.", "jurisdiction": "Tennessee" }, { "name": "Tesla Motors TX, Inc.", "jurisdiction": "Texas" }, { "name": "Tesla Motors UT, Inc.", "jurisdiction": "Utah" }, { "name": "Tesla Nambe LLC", "jurisdiction": "Delaware" }, { "name": "Tesla New Zealand ULC", "jurisdiction": "New Zealand" }, { "name": "Tesla Norway AS", "jurisdiction": "Norway" }, { "name": "Tesla Poland sp. z o.o.", "jurisdiction": "Poland" }, { "name": "Tesla Property &Casualty, Inc.", "jurisdiction": "California" }, { "name": "Tesla Portugal, Sociedade Unipessoal LDA", "jurisdiction": "Portugal" }, { "name": "Tesla Puerto Rico LLC", "jurisdiction": "Puerto Rico" }, { "name": "Tesla Pumps (Ningbo) Co.,LTD (fka: Hibar China Co. Ltd.)", "jurisdiction": "China" }, { "name": "Tesla Pumps Seoul Ltd.", "jurisdiction": "Republic of Korea" }, { "name": "Tesla Sales, Inc.", "jurisdiction": "Delaware" }, { "name": "Tesla Sdn. Bhd.", "jurisdiction": "" }, { "name": "Tesla Shanghai Co., Ltd", "jurisdiction": "Malaysia" }, { "name": "Tesla Spain, S.L. Unipersonal", "jurisdiction": "China" }, { "name": "Tesla Switzerland GmbH", "jurisdiction": "Spain" }, { "name": "Tesla (Thailand) Ltd.", "jurisdiction": "Switzerland" }, { "name": "Tesla TH1 LLC", "jurisdiction": "Thailand" }, { "name": "Tesla TH2 LLC", "jurisdiction": "Delaware" }, { "name": "Telsa Toronto Automation ULC", "jurisdiction": "Delaware" }, { "name": "Tesla Toronto International Holdings ULC", "jurisdiction": "Canada" }, { "name": "Tesla Transport B.V.", "jurisdiction": "Canada" }, { "name": "The Big Green Solar I, LLC", "jurisdiction": "Netherlands" }, { "name": "The Big Green Solar Manager I, LLC", "jurisdiction": "Delaware" }, { "name": "Three Rivers Solar 1, LLC", "jurisdiction": "Delaware" }, { "name": "Three Rivers Solar 2, LLC", "jurisdiction": "Delaware" }, { "name": "Three Rivers Solar 3, LLC", "jurisdiction": "Delaware" }, { "name": "Three Rivers Solar Manager 1, LLC", "jurisdiction": "Delaware" }, { "name": "Three Rivers Solar Manager 2, LLC", "jurisdiction": "Delaware" }, { "name": "Three Rivers Solar Manager 3, LLC", "jurisdiction": "Delaware" }, { "name": "TM International C.V.", "jurisdiction": "Netherlands" }, { "name": "TM Sweden AB", "jurisdiction": "Sweden" }, { "name": "USB SolarCity Manager IV, LLC", "jurisdiction": "Delaware" }, { "name": "USB SolarCity Master Tenant IV, LLC", "jurisdiction": "California" }, { "name": "USB SolarCity Owner IV, LLC", "jurisdiction": "California" }, { "name": "Visigoth Solar 1, LLC", "jurisdiction": "Delaware" }, { "name": "Visigoth Solar Holdings, LLC", "jurisdiction": "Delaware" }, { "name": "Visigoth Solar Managing Member 1, LLC", "jurisdiction": "Delaware" }, { "name": "VPP Project 1 (SA) Pty Ltd.", "jurisdiction": "Australia" }, { "name": "Weisshorn Solar I, LLC", "jurisdiction": "Delaware" }, { "name": "Weisshorn Solar Manager I, LLC", "jurisdiction": "Delaware" }, { "name": "Zep Solar LLC", "jurisdiction": "California" } ] }, { "id": "a78dec110cfe93c6778db19be2df9e57", "accessionNo": "0000950170-22-000796", "filedAt": "2022-02-04T20:11:27-05:00", "cik": "1318605", "ticker": "TSLA", "companyName": "Tesla, Inc.", "subsidiaries": [ { "name": "Allegheny Solar 1, LLC", "jurisdiction": "Delaware" }, { "name": "Allegheny Solar Manager 1, LLC", "jurisdiction": "Delaware" }, { "name": "Ancon Holdings II, LLC", "jurisdiction": "Delaware" }, // ... more subsidiaries { "name": "Firehorn Solar I, LLC", "jurisdiction": "Cayman Islands" }, { "name": "IL Buono Solar I, LLC", "jurisdiction": "Delaware" }, { "name": "Iliosson, S.A. de C.V.", "jurisdiction": "Mexico" }, { "name": "Maxwell Holding GmbH", "jurisdiction": "Germany" }, { "name": "Maxwell Technologies GmbH", "jurisdiction": "Germany" }, { "name": "NBA SolarCity AFB, LLC", "jurisdiction": "California" }, { "name": "Sequoia SolarCity Owner I, LLC", "jurisdiction": "Delaware" }, { "name": "Sierra Solar Power (Hong Kong) Limited", "jurisdiction": "Hong Kong" }, { "name": "TBM Partnership II, LLC", "jurisdiction": "Delaware" }, { "name": "TEO Engineering, Inc.", "jurisdiction": "California" }, { "name": "Tesla Automation GmbH", "jurisdiction": "Germany" }, { "name": "Tesla Automobile Information Service (Dalian) Co., Ltd.", "jurisdiction": "China" }, { "name": "Tesla Automobile Sales and Service (Shanghai) Co., Ltd.", "jurisdiction": "China" }, { "name": "Tesla Financial Leasing (China) Co., Ltd.", "jurisdiction": "China" }, { "name": "Tesla Financial Services GmbH", "jurisdiction": "Germany" }, { "name": "Tesla Financial Services Holdings B.V.", "jurisdiction": "Netherlands" }, { "name": "Tesla Financial Services Limited", "jurisdiction": "United Kingdom" }, { "name": "Tesla France S.à r.l.", "jurisdiction": "France" }, { "name": "Tesla Germany GmbH", "jurisdiction": "Germany" }, { "name": "Tesla Greece Single Member P.C.", "jurisdiction": "Greece" }, { "name": "Tesla Hrvatska d.o.o.", "jurisdiction": "Croatia" }, { "name": "Tesla Hungary Kft.", "jurisdiction": "Hungary" }, { "name": "Tesla India Motors and Energy Private Limited", "jurisdiction": "India" }, { "name": "Tesla Insurance Ltd.", "jurisdiction": "Malta" }, { "name": "Tesla Insurance Services, Inc.", "jurisdiction": "California" }, { "name": "Tesla Insurance Services of Texas, Inc.", "jurisdiction": "Texas" }, { "name": "Tesla International B.V.", "jurisdiction": "Netherlands" }, { "name": "Tesla Italy S.r.l.", "jurisdiction": "Italy" }, { "name": "Tesla Jordan Car Trading LLC", "jurisdiction": "Jordan" }, { "name": "Tesla Korea Limited", "jurisdiction": "Republic of Korea" }, { "name": "Tesla Motors Australia, Pty Ltd", "jurisdiction": "Australia" }, { "name": "Tesla Motors Austria GmbH", "jurisdiction": "Austria" }, { "name": "Tesla Motors (Beijing) Co., Ltd.", "jurisdiction": "China" }, { "name": "Tesla Motors Canada ULC", "jurisdiction": "Canada" }, { "name": "Tesla Motors Coöperatief U.A.", "jurisdiction": "Netherlands" }, { "name": "Tesla Motors Denmark ApS", "jurisdiction": "Denmark" }, { "name": "Tesla Motors FL, Inc.", "jurisdiction": "Florida" }, { "name": "Tesla Motors HK Limited", "jurisdiction": "Hong Kong" }, { "name": "Tesla Motors Iceland ehf.", "jurisdiction": "Iceland" }, { "name": "Tesla Motors Ireland Limited", "jurisdiction": "Ireland" }, { "name": "Tesla Motors Israel Ltd.", "jurisdiction": "Israel" }, { "name": "Tesla Motors Japan GK", "jurisdiction": "Japan" }, { "name": "Tesla Motors Limited", "jurisdiction": "United Kingdom" }, { "name": "Tesla Motors Luxembourg S.à r.l.", "jurisdiction": "Luxembourg" }, { "name": "Tesla Motors MA, Inc.", "jurisdiction": "Massachusetts" }, { "name": "Tesla Motors Netherlands B.V.", "jurisdiction": "Netherlands" }, { "name": "Tesla Motors Romania S.R.L.", "jurisdiction": "Romania" }, { "name": "Tesla Motors Sales and Service LLC", "jurisdiction": "Turkey" }, { "name": "Tesla Motors Singapore Holdings Pte. Ltd.", "jurisdiction": "Singapore" }, { "name": "Tesla Motors Singapore Private Limited", "jurisdiction": "Singapore" }, { "name": "Tesla Motors Stichting", "jurisdiction": "Netherlands" }, { "name": "Tesla Motors Taiwan Limited", "jurisdiction": "Taiwan" }, { "name": "Tesla Motors TN, Inc.", "jurisdiction": "Tennessee" }, { "name": "Tesla Motors TX, Inc.", "jurisdiction": "Texas" }, { "name": "Tesla Motors UT, Inc.", "jurisdiction": "Utah" }, { "name": "Tesla Nambe LLC", "jurisdiction": "Delaware" }, { "name": "Tesla New Zealand ULC", "jurisdiction": "New Zealand" }, { "name": "Tesla Norway AS", "jurisdiction": "Norway" }, { "name": "Tesla Poland sp. z o.o.", "jurisdiction": "Poland" }, { "name": "Tesla Portugal, Sociedade Unipessoal LDA", "jurisdiction": "Portugal" }, { "name": "Tesla Puerto Rico LLC", "jurisdiction": "Puerto Rico" }, { "name": "Tesla Pumps (Ningbo) Co.,LTD (fka: Hibar China Co. Ltd.)", "jurisdiction": "China" }, { "name": "Tesla Pumps Seoul Ltd.", "jurisdiction": "Republic of Korea" }, { "name": "Tesla Sales, Inc.", "jurisdiction": "Delaware" }, { "name": "Tesla Services Sdn. Bhd.", "jurisdiction": "Malaysia" }, { "name": "Tesla Shanghai Co., Ltd", "jurisdiction": "China" }, { "name": "Tesla Spain, S.L. Unipersonal", "jurisdiction": "Spain" }, { "name": "Tesla Switzerland GmbH", "jurisdiction": "Switzerland" }, { "name": "Telsa Toronto Automation ULC", "jurisdiction": "Canada" }, { "name": "Tesla Toronto International Holdings ULC", "jurisdiction": "Canada" }, { "name": "TM International C.V.", "jurisdiction": "Netherlands" }, { "name": "TM Sweden AB", "jurisdiction": "Sweden" }, { "name": "VPP Project 1 (SA) Pty Ltd.", "jurisdiction": "Australia" }, { "name": "Weisshorn Solar I, LLC", "jurisdiction": "Delaware" }, { "name": "Weisshorn Solar Manager I, LLC", "jurisdiction": "Delaware" }, { "name": "Zep Solar LLC", "jurisdiction": "California" } ] }, { "id": "de534eefa81872db7567bf7b990c6aff", "accessionNo": "0001564590-21-004599", "filedAt": "2021-02-08T07:27:23-05:00", "cik": "1318605", "ticker": "TSLA", "companyName": "Tesla, Inc.", "subsidiaries": [ { "name": "Allegheny Solar 1, LLC", "jurisdiction": "Delaware" }, { "name": "Allegheny Solar Manager 1, LLC", "jurisdiction": "Delaware" }, { "name": "Ancon Holdings II, LLC", "jurisdiction": "Delaware" }, { "name": "Ancon Holdings III, LLC", "jurisdiction": "Delaware" }, { "name": "Ancon Holdings, LLC", "jurisdiction": "Delaware" }, { "name": "Ancon Solar Corporation", "jurisdiction": "Delaware" }, // ... more subsidiaries { "name": "Weisshorn Solar Manager I, LLC", "jurisdiction": "Delaware" }, { "name": "Zep Solar Hong Kong Limited", "jurisdiction": "Hong Kong" }, { "name": "Zep Solar LLC", "jurisdiction": "California" } ] }, { "id": "bf4503aff887340e1202d684708f5d37", "accessionNo": "0001564590-20-004475", "filedAt": "2020-02-13T07:12:18-05:00", "cik": "1318605", "ticker": "TSLA", "companyName": "Tesla, Inc.", "subsidiaries": [ { "name": "Allegheny Solar 1, LLC", "jurisdiction": "Delaware" }, { "name": "Allegheny Solar Manager 1, LLC", "jurisdiction": "Delaware" }, { "name": "Ancon Holdings II, LLC", "jurisdiction": "Delaware" }, // ... more subsidiaries { "name": "VPP Project 1 (SA) Pty Ltd.", "jurisdiction": "Australia" }, { "name": "Weisshorn Solar I, LLC", "jurisdiction": "Delaware" }, { "name": "Weisshorn Solar Manager I, LLC", "jurisdiction": "Delaware" }, { "name": "Zep Solar Hong Kong Limited", "jurisdiction": "Hong Kong" }, { "name": "Zep Solar LLC", "jurisdiction": "California" }, { "name": "Zep Solar Trading Ltd", "jurisdiction": "China" } ] } ] } ``` ## FAQ Common questions about querying the Company Subsidiaries Database API, the response shape, and the bulk archives. ### How do I pull the full list of legal entities (subsidiaries) that a specific public company owns? To pull the legal entities a public company owns, query the `/subsidiaries` endpoint and filter on the parent company's ticker (`ticker`). For Tesla, the filter is the ticker field set to `TSLA`. The response returns one document per Exhibit 21 disclosure with the parent identifiers on `cik`, `ticker`, and `companyName`, and the legal-entity list on `subsidiaries`, where each item has a `subsidiaries.name` and a `subsidiaries.jurisdiction`. Because a company files Exhibit 21 every year, the most recent document in the response (the first one, since the default sort orders by `filedAt` descending) represents the company's current subsidiary footprint. Each entry in that `subsidiaries` array is one owned legal entity such as `Tesla Germany GmbH` or `Tesla Energy Operations, Inc.`. ```json { "query": "ticker:TSLA", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How can I look up every subsidiary list a company has ever reported, going back to 2003? To retrieve every subsidiary list a company has ever reported, query the `/subsidiaries` endpoint and filter on either the parent's ticker (`ticker`) or its CIK (`cik`). The dataset covers Exhibit 21 disclosures from 2003 to the present, so a single ticker filter returns one document per yearly filing. Each document is identified by `accessionNo` and dated by `filedAt`, and carries its own snapshot of the `subsidiaries` array. The default sort is by `filedAt` descending, so the most recent disclosure comes first. Paginate through the full history by incrementing `from` by 50 until you have consumed `total.value` results. ```json { "query": "ticker:MSFT", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I find the subsidiary disclosures of a company when I only know its CIK and not its ticker? To find a company's subsidiary disclosures by CIK alone, query the `/subsidiaries` endpoint and filter on the parent's `cik` field. For Tesla, set `cik` to `1318605`; the response carries the same Exhibit 21 documents you would get by ticker, with the parent identifiers on `cik`, `ticker`, and `companyName`. CIK is the most reliable identifier because some smaller filers and older subsidiary-only filers have no ticker at all — the `ticker` field on those documents is an empty string. If you only have a company name and need to resolve it to a CIK first, the `/mapping/name/` endpoint on the Mapping API performs that lookup. ```json { "query": "cik:1318605", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I pull subsidiary lists for several companies in one query? To pull subsidiary lists for several companies in one call, query the `/subsidiaries` endpoint and filter the `cik` (or `ticker`) field to any of a set of values. For Ford and Tesla, the `cik` field should match either `37996` or `1318605`; the response interleaves the documents of both parents, ordered by `filedAt` descending by default. Each result document keeps its own `cik`, `ticker`, and `companyName`, so you can group results client-side per parent. Combining identifiers this way is useful for peer-set or competitor comparisons. ```json { "query": "cik:(37996 1318605)", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I search for the subsidiary disclosure attached to a specific filing if I already have its accession number? To pull the subsidiary disclosure for one specific filing, query the `/subsidiaries` endpoint and filter on `accessionNo` set to the filing's accession number, for example `0000950170-23-001409`. The response is a single document whose `subsidiaries` array carries the parsed Exhibit 21 list — each item with a `subsidiaries.name` and a `subsidiaries.jurisdiction` — along with the parent's `cik`, `ticker`, `companyName`, and the `filedAt` timestamp of the underlying filing. ```json { "query": "accessionNo:\"0000950170-23-001409\"", "from": 0, "size": 50 } ``` ### How do I retrieve every subsidiary disclosure filed within a specific calendar year? To retrieve every subsidiary disclosure made in a given calendar year, query the `/subsidiaries` endpoint and constrain the `filedAt` field to dates between January 1 and December 31 of that year. For 2020, the value of `filedAt` should fall between `2020-01-01` and `2020-12-31`. The response carries `total.value` matching documents (typically around 7,000 per year across all public filers). Page through them by incrementing `from` by 50, and sort by `filedAt` ascending or descending depending on whether you want the chronological start or end of the year first. ```json { "query": "filedAt:[2020-01-01 TO 2020-12-31]", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I find all U.S.-listed companies that have a subsidiary incorporated in China? To find U.S.-listed parents with a subsidiary incorporated in China, query the `/subsidiaries` endpoint and filter on the nested jurisdiction of the subsidiary entries — the value of `subsidiaries.jurisdiction` should be `China`. Each matching document carries the parent's `cik`, `ticker`, and `companyName`, and the entire `subsidiaries` array of that filing. Real Exhibit 21 disclosures sometimes use alternate wording for the same jurisdiction (for example `PRC` for People's Republic of China, or compound strings such as `Hong Kong` for the SAR), so combine `China` with those variants when you want a complete picture. The `subsidiaries.name` of each matching child entity (for example `Tesla Shanghai Co., Ltd`) tells you which specific legal entities are based there. ```json { "query": "subsidiaries.jurisdiction:China OR subsidiaries.jurisdiction:PRC", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I list every company with operating units in well-known offshore tax havens such as the Cayman Islands, Bermuda, or Luxembourg? To list parents with operating units in offshore tax havens, query the `/subsidiaries` endpoint and filter the nested `subsidiaries.jurisdiction` field to any of `Cayman Islands`, `Bermuda`, or `Luxembourg`. Each matching document represents one Exhibit 21 filing, with the parent on `cik`, `ticker`, and `companyName` and the full `subsidiaries` list attached. For a complete coverage list, extend the jurisdiction set with other commonly cited havens such as `British Virgin Islands`, `Jersey`, `Guernsey`, `Isle of Man`, `Mauritius`, and `Singapore`. The matching entries inside `subsidiaries` give you the specific legal entities — for example `Cobalt International Energy Overseas Ltd.` in the Cayman Islands or `Stream International (Bermuda) Ltd.` in Bermuda. ```json { "query": "subsidiaries.jurisdiction:(\"Cayman Islands\" OR \"Bermuda\" OR \"Luxembourg\")", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How can I find which large U.S. companies have entities registered in sanctioned or high-risk jurisdictions? To find U.S. filers with entities in sanctioned or high-risk jurisdictions, query the `/subsidiaries` endpoint and filter the nested `subsidiaries.jurisdiction` field to the jurisdictions of interest — for example `Russia`, `Iran`, `Cuba`, `Syria`, `North Korea`, `Belarus`, `Venezuela`, or `Myanmar`. Each matching document is one Exhibit 21 filing, with the parent identifiers on `cik`, `ticker`, and `companyName` and the offending subsidiaries inside the `subsidiaries` array. Because Exhibit 21 is plain-text-derived, jurisdictions are sometimes phrased differently across filings (for example `Russian Federation` instead of `Russia`, or `Islamic Republic of Iran` instead of `Iran`). Querying for both variants and de-duplicating client-side by `cik` gives a cleaner list of distinct parents. ```json { "query": "subsidiaries.jurisdiction:(\"Russia\" OR \"Russian Federation\" OR \"Iran\" OR \"Cuba\" OR \"Syria\" OR \"North Korea\" OR \"Belarus\" OR \"Venezuela\" OR \"Myanmar\")", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I locate every parent company that owns a subsidiary with a specific name, like "Maxwell Technologies"? To locate the parent of a named subsidiary, query the `/subsidiaries` endpoint and filter on the nested subsidiary name — the value of `subsidiaries.name` should match `Maxwell Technologies` (allow a trailing wildcard so you also catch variants like `Maxwell Technologies GmbH` or `Maxwell Holding GmbH`). Each matching document carries the parent on `cik`, `ticker`, and `companyName`, plus the `filedAt` of the filing where the name was disclosed. A child entity can appear under different parents over time if it has been acquired or divested, so grouping the matches by `cik` reveals the ownership history of the named subsidiary. ```json { "query": "subsidiaries.name:Maxwell*", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I search for subsidiaries whose names contain a particular keyword such as "Insurance" or "Leasing"? To search for subsidiaries by a keyword in their name, query the `/subsidiaries` endpoint and filter on the nested `subsidiaries.name` field with a wildcard around the keyword — for example a wildcard match that contains `Insurance` will pull entities such as `Tesla Insurance, Inc.`, `Tesla Insurance Brokers Co., Ltd.`, and `Tesla General Insurance, Inc.`. The same pattern with `Leasing` surfaces entities like `Tesla Financial Leasing (China) Co., Ltd.`. Matches are returned as full Exhibit 21 documents, so each result still includes the parent on `cik`, `ticker`, and `companyName`. You can then post-process the `subsidiaries` array client-side to keep only the entries whose `subsidiaries.name` actually contains the keyword. ```json { "query": "subsidiaries.name:*Insurance*", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I track how a company's subsidiary footprint has evolved year over year? To track how a company's subsidiary footprint evolves over time, query the `/subsidiaries` endpoint filtering on `ticker` (or `cik`) and sort by `filedAt` ascending so the oldest disclosure is first. Each year's Exhibit 21 comes back as a separate document, with the snapshot of legal entities at that point in time inside its `subsidiaries` array. With the documents in chronological order, compare successive `subsidiaries.name` lists pairwise client-side: names that appear in year N but not in year N−1 are new entities, and names dropped from year N+1 are divested or dissolved. The `subsidiaries.jurisdiction` of each name lets you also chart geographic expansion or contraction year over year. ```json { "query": "ticker:TSLA", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"asc"}}] } ``` ### How can I detect newly added subsidiaries between a company's most recent disclosure and its prior one? To detect newly added subsidiaries between two consecutive disclosures, query the `/subsidiaries` endpoint filtering on the company's `ticker` (or `cik`), keep the default sort by `filedAt` descending, and request the first two documents. The response carries the latest Exhibit 21 first and the prior year's second, each with its own `subsidiaries` array. Client-side, compare the set of `subsidiaries.name` values from the latest document with the set from the prior one — names present only in the latest are the newly added entities. Their `subsidiaries.jurisdiction` value tells you where the new entity is registered, which often signals an entry into a new market. ```json { "query": "ticker:TSLA", "from": 0, "size": 2, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How can I identify subsidiaries that a company has dropped (divested or dissolved) compared with the prior year? To find subsidiaries a company has dropped, query the `/subsidiaries` endpoint filtering on the parent's `cik` (or `ticker`) and retrieve the two most recent Exhibit 21 documents in `filedAt` descending order. Each document carries its own snapshot of the `subsidiaries` array. Client-side, take the set of `subsidiaries.name` values from the older document and subtract the set from the newer one — what remains is the set of entities that disappeared between filings, indicating a divestiture, dissolution, or merger of those legal entities. Cross-reference the `subsidiaries.jurisdiction` to spot whether the company has fully exited a particular country. ```json { "query": "cik:1318605", "from": 0, "size": 2, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I find which Delaware-incorporated entities are owned by a given parent? To find a parent's Delaware-incorporated entities, query the `/subsidiaries` endpoint and filter on both identifiers together: the `ticker` field should equal the parent's ticker (for example `TSLA`) and the nested `subsidiaries.jurisdiction` field should equal `Delaware`. The response returns the parent's Exhibit 21 documents in which at least one subsidiary is incorporated in Delaware. The document-level match does not restrict the `subsidiaries` array itself, so iterate through it client-side and keep only entries whose `subsidiaries.jurisdiction` equals `Delaware` — for Tesla these include `Tesla Energy Operations, Inc.`, `Tesla Finance LLC`, and `Tesla Insurance Holdings, LLC`. ```json { "query": "ticker:TSLA AND subsidiaries.jurisdiction:Delaware", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I count how many international subsidiaries a company holds outside the United States? To count a company's international subsidiaries, query the `/subsidiaries` endpoint filtering on the parent's `cik` (or `ticker`) and take the most recent document by `filedAt`. Then walk the `subsidiaries` array client-side and count entries whose `subsidiaries.jurisdiction` is not a US state, US territory, or the United States itself. A pragmatic approach is to build a whitelist of US-domestic values — the fifty state names, `District of Columbia`, `Puerto Rico`, `Guam`, and free-text values such as `Delaware, USA` or `Arizona, USA` that some filers use — then count every `subsidiaries.jurisdiction` outside that list as international. Treat entries where `subsidiaries.jurisdiction` is an empty string as unknown rather than international. ```json { "query": "ticker:TSLA", "from": 0, "size": 1, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I find companies whose subsidiaries are concentrated in a single foreign country, e.g. companies with many Irish subsidiaries? To find parents heavily concentrated in a single foreign country, query the `/subsidiaries` endpoint filtering the nested `subsidiaries.jurisdiction` field to that country — for Ireland the value should be `Ireland`. The response carries every Exhibit 21 document with at least one Irish subsidiary, identified by the parent's `cik`, `ticker`, and `companyName`. Group the results client-side by `cik` (keeping the most recent disclosure per company by `filedAt`) and, within that latest document, count the entries in `subsidiaries` whose `subsidiaries.jurisdiction` equals `Ireland`. Sorting parents by that count surfaces the filers whose international footprint is most heavily skewed toward Ireland. ```json { "query": "subsidiaries.jurisdiction:Ireland", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How can I pull every Exhibit 21 disclosure made in the last 30 days to monitor newly reported corporate structures? To monitor newly reported corporate structures, query the `/subsidiaries` endpoint and filter `filedAt` to dates within the last 30 days (the start of the window should be 30 days before today, and the end should be today). Sort by `filedAt` descending so the most recent disclosures arrive first. The response carries each new filing as a full document with the parent on `cik`, `ticker`, and `companyName`, the unique `accessionNo` of the underlying SEC filing, and the parsed `subsidiaries` array. Paginate by incrementing `from` by 50 until you have read `total.value` results. ```json { "query": "filedAt:[2026-04-26 TO 2026-05-26]", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I paginate through more than 50 subsidiary lists when a query returns thousands of matches? The `/subsidiaries` endpoint returns at most 50 documents per call (the maximum value of `size`). To page beyond the first 50, repeat the same query and increase `from` by `size` each call — `from` set to `0`, then `50`, then `100`, and so on — until you have consumed `total.value` matches. Keep `sort` stable across requests (the default is `filedAt` descending) so the pagination window remains consistent and no document is skipped or duplicated between pages. ```json { "query": "filedAt:[2020-01-01 TO 2020-12-31]", "from": 50, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I see the total number of subsidiary lists that match a query without downloading all of them? Every response from the `/subsidiaries` endpoint includes a `total` object whose `total.value` field reports the total number of Exhibit 21 documents that match the query — independent of how many are returned in the current page. To read the count without downloading the data itself, issue the query with `size` set to `0` (or `1`) and inspect `total.value` in the response. ```json { "query": "ticker:TSLA", "from": 0, "size": 0, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I sort subsidiary disclosures from oldest to newest instead of the default newest-first? The default sort on the `/subsidiaries` endpoint is by `filedAt` descending. To return the oldest disclosures first instead, set the `sort` array to order by `filedAt` ascending. The result documents are then ordered chronologically from the earliest Exhibit 21 (back to 2003) forward, which is convenient for building historical timelines. ```json { "query": "ticker:MSFT", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"asc"}}] } ``` ### How can I retrieve the very first subsidiary disclosure a company made after 2003? To retrieve a company's very first Exhibit 21 disclosure in the database, query the `/subsidiaries` endpoint filtering on the parent's `ticker` or `cik`, set `sort` to order by `filedAt` ascending, and set `size` to `1`. The single document returned is the earliest disclosure on file for that parent (the dataset starts in 2003), with its `filedAt`, `accessionNo`, and original `subsidiaries` snapshot. ```json { "query": "ticker:TSLA", "from": 0, "size": 1, "sort": [{"filedAt":{"order":"asc"}}] } ``` ### How do I extract a clean JSON list of subsidiaries from a specific Exhibit 21 filing by passing in just its accession number? To extract a clean JSON list of subsidiaries from a specific Exhibit 21, query the `/subsidiaries` endpoint and filter on `accessionNo` set to the filing's accession number (for example `0000950170-23-001409`). The response is the single document for that filing, with the parsed list on `subsidiaries` — each entry containing `subsidiaries.name` and `subsidiaries.jurisdiction` — alongside the parent's `cik`, `ticker`, `companyName`, and the `filedAt` timestamp. The accession number is the same identifier that appears in the URL of the exhibit on EDGAR, so this is the right path when you already have a link to a specific Exhibit 21 and want the structured data behind it. ```json { "query": "accessionNo:\"0000950170-23-001409\"", "from": 0, "size": 50 } ``` ### How do I search the subsidiary database by the parent company's name when I don't know its ticker? To search by parent company name, query the `/subsidiaries` endpoint and filter on `companyName` with a wildcard — for example `companyName` matching anything starting with `Tesla` returns every Exhibit 21 disclosure whose parent name begins with `Tesla`. Each matching document still carries the parent's `cik` and `ticker` if available, which you can use as a more stable identifier for follow-up queries. If you would rather resolve the name to a single CIK first, the `/mapping/name/` endpoint on the Mapping API performs that lookup and you can then filter `/subsidiaries` by `cik` instead. ```json { "query": "companyName:Tesla*", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How can I find companies that disclose entities in multiple foreign jurisdictions in a single filing? To find companies whose Exhibit 21 lists entities in multiple foreign jurisdictions at once, query the `/subsidiaries` endpoint and require all of the desired jurisdictions on the nested `subsidiaries.jurisdiction` field — for example `subsidiaries.jurisdiction` should include both `China` and `Germany`. Each matching document is one filing in which both conditions are satisfied somewhere in the `subsidiaries` array. The document-level match does not tell you which specific entities are in which country, so walk `subsidiaries` client-side and group entries by their `subsidiaries.jurisdiction` to see the full multi-country footprint of that parent for that filing. ```json { "query": "subsidiaries.jurisdiction:China AND subsidiaries.jurisdiction:Germany", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I compare the international footprints of two competitors side by side? To compare two competitors side by side, query the `/subsidiaries` endpoint and filter `cik` to either of the two companies (for example `1318605` for Tesla and `1467858` for General Motors), sorted by `filedAt` descending. The response interleaves their Exhibit 21 documents; keep the most recent one per `cik` to get a current snapshot of each. For each parent, group entries in `subsidiaries` by `subsidiaries.jurisdiction` and count them. Laying the two jurisdiction-to-count maps next to each other reveals where each competitor has a presence the other does not, and where their footprints overlap. ```json { "query": "cik:(1318605 1467858)", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I find subsidiaries of a delisted or acquired company that no longer files with the SEC? The subsidiary database is survivorship-bias free — it preserves Exhibit 21 disclosures from companies that have since been acquired, gone private, or delisted. To pull such a company's subsidiaries, query the `/subsidiaries` endpoint filtering on its historical `cik` (the most stable identifier) or its `ticker` while it was still trading. The response returns every Exhibit 21 the company ever filed, with `filedAt` showing when each snapshot was disclosed. Because the company no longer files, the latest document by `filedAt` represents its final disclosed subsidiary structure before delisting. If you only know a former name, the `/mapping/name/` endpoint on the Mapping API can resolve it to a CIK. ```json { "query": "cik:1310067", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I write a Lucene query that combines a date range with a jurisdiction filter, e.g. all Chinese subsidiaries disclosed in 2022? To combine a date range with a jurisdiction filter on the `/subsidiaries` endpoint, require both conditions in one query: the value of `subsidiaries.jurisdiction` should be `China` and the value of `filedAt` should fall between `2022-01-01` and `2022-12-31`. The response carries every Exhibit 21 document filed in 2022 that has at least one subsidiary registered in China, with the parent on `cik`, `ticker`, and `companyName`. Page through the results by incrementing `from` by 50 against `total.value`, and walk each document's `subsidiaries` array client-side to extract the specific Chinese entities — entries where `subsidiaries.jurisdiction` equals `China`. ```json { "query": "subsidiaries.jurisdiction:China AND filedAt:[2022-01-01 TO 2022-12-31]", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ### How do I handle subsidiary records where the jurisdiction field is reported as an empty string in older filings? In older Exhibit 21 filings — especially those from the early 2000s — the parser sometimes cannot recover the place of incorporation, and the `subsidiaries.jurisdiction` field is stored as an empty string rather than being absent. The `/subsidiaries` endpoint returns these records as-is. Treat an empty-string `subsidiaries.jurisdiction` as missing data on your side: filter such entries out before computing jurisdiction-based aggregates so you do not double-count them as either domestic or international, and do not try to match them via a jurisdiction filter (a value-based filter for a specific country never returns them). Entries where `subsidiaries.jurisdiction` is a non-empty country or state value should be used as authoritative. ```json { "query": "NOT subsidiaries.jurisdiction:*", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"asc"}}] } ``` ### How do I find subsidiary disclosures whose parent company has no ticker symbol on record, such as private filers or delisted entities? To pull Exhibit 21 disclosures whose parent company does not have a ticker on record, query the `/subsidiaries` endpoint and require the parent's `ticker` field to be empty — the value of `ticker` should be an empty string, since the dataset stores the field as "" rather than dropping it when the parent has no listed symbol. This pattern is common for subsidiary-only filers (entities that file Exhibit 21 as part of a 10-K but never had a publicly listed equity), for private debt issuers, and for companies that have since gone private or delisted. Once a matching document is in hand, the parent is identified by its CIK (`cik`) and its legal name (`companyName`); the parsed Exhibit 21 list sits on `subsidiaries`, with each entry's name on `subsidiaries.name` and place of incorporation on `subsidiaries.jurisdiction`. Because `cik` is always present and stable across renames, use it as the canonical identifier for follow-up queries. The `/mapping` endpoint resolves a CIK to any other identifiers EDGAR has on file for that filer. ```json { "query": "NOT ticker:?*", "from": 0, "size": 50, "sort": [{"filedAt":{"order":"desc"}}] } ``` ## References Refer to the following resources for more information about Exhibit 21 and lists of subsidiaries: - [17 CFR § 229.601 - (Item 601) Exhibits](https://www.ecfr.gov/current/title-17/chapter-II/part-229/subpart-229.600/section-229.601) ### Papers & Research - [Strategic Subsidiary Disclosure](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=3137138) - [The Disclosure and Valuation of Foreign Cash Holdings](https://papers.ssrn.com/sol3/papers.cfm?abstract_id=2558350)