Documentation Index
Fetch the complete documentation index at: https://docs.wokelo.ai/llms.txt
Use this file to discover all available pages before exploring further.
1. Overview
The Industry Deep Intelligence API generates structured, source-cited intelligence on any industry or sector. Unlike the Industry Research Workflow (which always produces a fixed five-section report via an async job system), this API lets you select exactly which sections you need — requesting only market sizing, or only M&A activity, or any combination of the ten available section types — and returns results through a lightweight async polling loop. This is an asynchronous POST API — submitting a request returns arequest_id (a UUID string) and an initial "PENDING" status immediately. You then poll the Request Status endpoint with that request_id until the status becomes "COMPLETED", at which point the full result is embedded directly in the status response.
The two-step workflow:
This API uses a different async pattern from the Workflow APIs (Company Research, Industry Research, Peer Comparison, Custom Workflow). Those APIs use
report_id (integer) with separate submission and download steps. This API uses request_id (UUID string) and embeds the completed result directly in the status polling response — no separate download call is needed.| Section | What you get |
|---|---|
market_size | TAM/SAM estimates from multiple tier-1 publishers, with a multi-source chart showing CAGR ranges and projected end values |
quant_insights | Quantitative data points: growth rates, adoption metrics, cost benchmarks, and other measurable market signals |
trends_and_innovations | Technology trends, innovation waves, disruption signals, and named company examples — source-cited markdown narrative |
transactions_mna | M&A deal flow: acquirers, targets, deal values, and strategic rationale |
transactions_fundraising | VC/PE activity: rounds, valuations, key investors, and sector heatmap |
transactions_ipo | IPO exits: companies, valuations, tickers, and listing dates |
partnerships | Strategic partnership mapping across the industry with key actors and deal structures |
tier1_intelligence | Curated insights sourced exclusively from McKinsey, BCG, Goldman Sachs, and equivalent tier-1 publishers |
case_studies | In-depth profiles of 3–4 key companies with strategy timelines and competitive positioning |
industry_regulations | Regulatory environment: active legislation, compliance requirements, enforcement trends, and jurisdictional differences |
- Market entry sizing — request
market_size+quant_insightsfor a new sector before committing diligence resources; get a multi-source CAGR range immediately - Deal sourcing intelligence — request
transactions_mna+transactions_fundraisingto surface active deal flow and recently funded companies in a space - IC memo background research — request
tier1_intelligence+trends_and_innovationsfor a concise, credible sector context block with McKinsey/BCG sourcing - Regulatory risk assessment — request
industry_regulationsfor a specific geography to map compliance requirements for a target sector - Competitive case study analysis — request
case_studiesto rapidly profile 3–4 key players in a market before a competitive diligence sprint - Modular pipeline enrichment — run specific sections on multiple sectors in parallel and stitch results into a unified research database
This API is asynchronous. Submit a request, then poll until
status = "COMPLETED". See How Async APIs work for a full explanation of the polling lifecycle.2. Quick Start
Step 1 — Submit a request3. Authentication
All requests must include a Bearer token in theAuthorization HTTP header.
4. Request Reference
Endpoint| Parameter | Type | Required | Description |
|---|---|---|---|
topic | string | Required | The industry, sector, or theme to analyse. Free-text — specificity directly determines report quality. Examples: "Enterprise SaaS security", "AI in drug discovery", "Lithium-ion battery manufacturing". Also accepted as "industry" in some client implementations. |
sections | string[] | Required | Array of one or more section identifiers to include in the output. Request only what you need — each section adds processing time. See the supported sections table below. |
parameters | object | Optional | A nested object containing optional refinement filters. All child fields are optional. |
parameters.keywords | string[] | Optional | Focus keywords to narrow the analysis within the topic. Examples: ["zero trust", "SIEM"], ["drug discovery", "AlphaFold"]. |
parameters.geography | string[] | Optional | Array of ISO 3166-1 alpha-3 country codes to scope the analysis geographically. Examples: ["USA"], ["GBR", "DEU", "FRA"]. |
parameters.definition | string | Optional | A custom plain-English definition of the industry to guide AI analysis scope. Use this when the topic string alone is ambiguous. Example: "B2B software focused on enterprise cybersecurity, excluding consumer antivirus products". |
parameters.sample_companies | string[] | Optional | Array of Wokelo/Crunchbase permalinks for representative companies in the industry. Helps ground the analysis in the correct competitive set. Examples: ["crowdstrike", "sentinelone", "palo-alto-networks"]. |
| Section value | Description |
|---|---|
market_size | TAM/SAM/SOM estimates sourced from multiple tier-1 market research publishers. Returns a structured market_size_chart object with per-publisher CAGR, start value, end value, and projection year — plus a pre-rendered chart image URL. |
quant_insights | Quantitative data: growth rates, adoption metrics, cost benchmarks, and measurable market signals. |
trends_and_innovations | Technology trends, innovation waves, and disruption signals — markdown narrative with named company examples, fully source-cited. |
transactions_mna | M&A deal flow: acquirers, targets, deal values, and strategic rationale for key transactions in the space. |
transactions_fundraising | VC and PE activity: funding rounds, valuations, key investors, and a sector heatmap of capital flows. |
transactions_ipo | IPO exits: company names, valuations at listing, tickers, and listing dates. |
partnerships | Strategic partnership mapping across the industry — key actors, deal structures, and partnership types. |
tier1_intelligence | Curated insights drawn exclusively from McKinsey, BCG, Goldman Sachs, Bain, and equivalent tier-1 sources. |
case_studies | In-depth profiles of 3–4 key companies — strategy timelines, competitive positioning, and market role. |
industry_regulations | Regulatory environment: active legislation, compliance requirements, enforcement trends, and jurisdictional differences. |
5. Response
Submission response
The initial POST returns a202 Accepted with two fields:
| Field | Type | Description |
|---|---|---|
request_id | string (UUID) | Unique identifier for this request. Use it with the Request Status endpoint to poll for completion. Note: this is a UUID string, not an integer report_id — the two identifiers are not interchangeable. |
status | string | Initial status, always "PENDING" on submission. |
Status polling response
PollGET /api/enterprise/request/status/?request_id={request_id}. The status field progresses through the following values:
| Status value | Meaning |
|---|---|
"PENDING" | Request is queued, waiting to start. |
"PROCESSING" | Analysis is in progress. |
"COMPLETED" | All requested sections are ready. The full result is embedded in this response. |
"FAILED" | Request failed. Retry the submission. |
Completed result structure
When status is"COMPLETED", the polling response includes a result object. The result is structured as:
"IP enrichment". Your requested sections appear as child keys of this object, keyed by the section name you submitted.
meta object
| Field | Type | Description |
|---|---|---|
report_id | integer | Internal Wokelo report identifier for this enrichment run. Different from request_id. |
title | string | Auto-generated report title based on topic. |
user | string | Email address of the user associated with the API token. |
dt_createdon | string | Datetime the report was created, in YYYY-MM-DD HH:MM:SS format (UTC). |
Section-level response schemas
market_size
data array represents one market research publisher’s estimate. Values use the {value, multiplier} pattern — always multiply before presenting. cagr is a string (not a float) representing percentage.
trends_and_innovations
summary field is a full markdown narrative with bold topic headings, named company examples, quantified data points, and inline source brackets referencing the source array by id.
All other sections (quant_insights, transactions_mna, transactions_fundraising, transactions_ipo, partnerships, tier1_intelligence, case_studies, industry_regulations) follow the same general pattern as trends_and_innovations: a named sub-object containing a source array and a summary markdown string. Some sections may additionally include structured charts objects similar to market_size.
Market size
start_value, end_value, and estimated_value all use the {value, multiplier} encoding — the same pattern as Industry Research fundraising charts. Always compute value × multiplier to get the raw USD amount: 2.5 × 1,000,000,000 = $2.5B. The cagr field is a string, not a float; parse with float(entry["cagr"]) before arithmetic.6. Examples
Market sizing for a new sector
Request onlymarket_size for a fast, focused market sizing check before committing broader diligence.
Deal flow intelligence — M&A and fundraising
Request both transaction sections to surface active deal flow and recently funded companies for a target sector.IC memo background — tier-1 intelligence and trends
Pull McKinsey/BCG-sourced insights and innovation trends for a sector in a single call for an IC memo background section.Regulatory risk scan for a specific geography
Scopeindustry_regulations to a single country to assess jurisdiction-specific compliance requirements.
Full-section deep dive
Request all ten sections for a comprehensive sector intelligence run.Batch analysis across multiple sectors
Run Industry Deep Intelligence on several sectors in parallel and collect all results.JavaScript / Node.js
7. Error Handling
The API uses standard HTTP status codes. The submission endpoint returns a202 on success and synchronous errors for invalid requests. Processing errors appear as "FAILED" status when polling.
| Status | Meaning | Cause & Resolution |
|---|---|---|
202 Accepted | Request accepted | request_id and "PENDING" status returned. Proceed to polling. |
400 Bad Request | Invalid parameters | Missing topic, invalid sections value, or malformed parameters object. Check the detail field and verify section names against the supported sections table. |
401 Unauthorized | Auth failed | The Authorization header is missing or contains an invalid token. Verify your key in Settings → API Keys. |
403 Forbidden | Insufficient access | Your plan does not include access to this endpoint or the requested sections. Contact support@wokelo.ai. |
429 Too Many Requests | Rate limit exceeded | Implement exponential back-off. The response includes a Retry-After header. |
500 Internal Server Error | Server error | Retry after a brief delay. If the issue persists, contact support@wokelo.ai. |
"FAILED" request status:
8. Best Practices
Request only the sections you need — each section adds processing time Unlike Workflow APIs that always generate a fixed full report, this API lets you select precisely the sections relevant to your use case. A single-sectionmarket_size request completes significantly faster than a full ten-section run. For tight turnaround use cases (IC prep, quick market checks), request one to three sections maximum:
topic string — it is the primary quality driver
The topic field is free-text and specificity directly determines how focused the output is. Vague topics produce generic, shallow results:
parameters.definition to resolve ambiguity when the topic alone is insufficient
When your topic string could be interpreted in multiple ways, the definition parameter anchors the analysis to your intended scope. This is particularly useful for topics that span consumer and enterprise, or that sit at the intersection of multiple industries:
request_id is a UUID string — it is not interchangeable with report_id
This API returns a UUID request_id (e.g. "c574254f-137d-40d5-84f1-ac8fa38b8aa7"). The Workflow APIs return an integer report_id. These use different polling endpoints and cannot be mixed:
POST /api/assets/download_report/ call after polling), this API embeds the full result in the status response when status == "COMPLETED". Extract data["result"] directly from the poll response:
market_size chart values with the {value, multiplier} pattern
Each market size data point stores values as {value, multiplier} pairs rather than raw numbers. Always multiply before presenting, and note that cagr is a string not a float:
parameters.sample_companies to ground the analysis in your competitive set
Providing representative company permalinks in sample_companies guides the AI analysis toward the right competitive context, particularly for niche sectors where the topic string alone might be interpreted too broadly. Use permalinks (not website URLs) — find them via the Company Search API:
9. Related APIs
Industry Research
The async Workflow alternative — generates a fixed five-section industry report with PDF/DOCX/PPT export. Use when you need a complete formatted deliverable.
Company Deep Intelligence
The company-level equivalent — section-selective deep intelligence on any specific company, using the same async request_id pattern.
Industry News Monitoring
Real-time news feed for any industry topic — synchronous, paginated, no polling required. Complements Industry Deep Intelligence for ongoing monitoring.
Market Map
Discover and map all companies competing in a specific market or product category — ideal to run alongside Industry Deep Intelligence for a competitive landscape.
Newsfeed
Structured multi-industry news feed filtered by sentiment, geography, and event category — for recurring sector monitoring pipelines.
Supporting APIs
Request Status and Company Search — both used alongside Industry Deep Intelligence in the async workflow.