Taxonomy APIs

APIs

Base URL:

https://app.daloopa.com/api/v3

All Taxonomy endpoints are GET and use Basic authentication.

Endpoint detail

List Taxonomy Metrics

Purpose: discover the available Taxonomy metrics, optionally filtered by company and series.

• GET /taxonomy/metrics
• Query params: company_id, series_id, keywords (array, max 15), limit, offset
• Docs: https://docs.daloopa.com/reference/list_taxonomy_metrics_v3

Retrieve Taxonomy Metric

Purpose: get detailed information about a single Taxonomy metric.

• GET /taxonomy/metrics/{id}
• Path param: id (required)
• Query params: company_id, industry_id, sector_id
• Docs: https://docs.daloopa.com/reference/retrieve_taxonomy_metric_v3

Retrieve Taxonomy Industry Template

Purpose: get the industry template for a given industry classification, including associated sectors and active template metrics with their company series.

• GET /taxonomy/industry-template/{industry_id}
• Path param: industry_id (required)
• Docs: https://docs.daloopa.com/reference/retrieve_taxonomy_industry_template_v3

List Taxonomy Industries

Purpose: retrieve industries and their member companies, with the option to resolve a company's industry and peer set.

• GET /taxonomy/industries
• Query params: company_id (returns that company's industry plus peers), sector_id (filter by GICS sector), limit, offset
• Docs: https://docs.daloopa.com/reference/list_taxonomy_industries

List Taxonomy Sectors

Purpose: retrieve sectors and the industries associated with each.

• GET /taxonomy/sectors
• Query params: limit, offset
• Docs: https://docs.daloopa.com/reference/list_taxonomy_sectors

Navigation flow A: hierarchy first

Use this when you are exploring, or when the question starts from a sector or a company.

1. GET /taxonomy/sectors to see the top level breakdown.
2. GET /taxonomy/industries?sector_id=... to pick an industry, or pass company_id to jump straight to a company's industry and peers.
3. GET /taxonomy/industry-template/{industry_id} to see the expected metric set for that industry and which company series populate it.
4. GET /taxonomy/metrics/{id} for the detail of any specific metric, scoped to a company where needed.

Navigation flow B: metric first, scoped by industry

Use this when you already know the concept you want and the open question is how it resolves across an industry. This is the natural flow for peer comparison and for coverage checks on a single metric.

1. GET /taxonomy/metrics?keywords=... to locate the metric in the canonical universe and capture its id. Keywords accept up to 15 terms, so several phrasings of the same concept can be tried in one call.
2. GET /taxonomy/industries to resolve the industry_id. Pass sector_id to narrow the list, or company_id if you know one company in the group and want the API to hand back its industry plus peers. The response also gives you the member companies, which becomes your expected denominator in step 4.
3. GET /taxonomy/metrics/{id}?industry_id=... to retrieve the metric scoped to that industry rather than globally. Swap in sector_id for a wider view, or company_id to drill down to a single company's series.
4. GET /taxonomy/industry-template/{industry_id} to place the metric in context: confirm it belongs to the industry's active template, see the sibling metrics in the same section, and compare the company series actually mapped against the member company list from step 2. Gaps between the two are your coverage holes.