Skip to main content

Overview

Several Wokelo APIs — including all Enrichment, Discovery, and Workflow Automation APIs — operate asynchronously. Because these operations involve deep AI research, large-scale data enrichment, and multi-source synthesis, they can take anywhere from a few seconds to 25 minutes to complete. Rather than keeping your HTTP connection open for that entire duration, Wokelo uses a Submit → Poll → Retrieve pattern. This means your integration is non-blocking: submit a job, move on, and fetch results when they’re ready.

Why Asynchronous?

Wokelo APIs produce intelligence at investment-grade quality — resolving entities across 20M+ companies, deduplicating signals from 1,000+ curated sources, and running structured AI workflows. This depth takes time. A synchronous API would require you to hold a connection open for up to 25 minutes, which is impractical for production systems. The async pattern lets you:
  • Decouple submission from retrieval — fire a job and handle the result whenever it’s ready
  • Handle long-running tasks reliably — no timeout failures on deep research jobs
  • Run multiple requests in parallel — submit many jobs simultaneously and poll each independently
  • Integrate cleanly into pipelines — queue results, trigger downstream workflows, or store outputs on completion

The Three-Step Flow

STEP 1: SUBMIT STEP 2: POLL STEP 3: RETRIEVE

Step 1 — Submit a Request

Call the relevant API endpoint with your parameters. The API returns immediately with a request_id (for Enrichment and Discovery APIs) or a report_id (for Workflow APIs). This ID is your handle for everything that follows. Example — Submitting a Market Map request:
Response:
Save the request_id. You will need it in Steps 2 and 3.

Which ID do I get?

Step 2 — Poll for Status

After submitting, periodically call the Request Status endpoint with your request_id to check progress. The API returns a status field that moves through the following states:

Status Lifecycle

Endpoint:
For request_id
For report_id
Example:
Response while processing:
Response when complete:
Do not poll too aggressively — it wastes quota and does not speed up results. Use an interval appropriate to the expected processing time:

Polling Code Examples

Step 3 — Retrieve Results

Once status is COMPLETED, fetch the full result payload using the Request Result endpoint. Endpoint: For request_id:
For report_id:
Example:
Response:
The result field contains structured, agent-ready JSON output — the exact schema varies by API type (enrichment fields for Enrichment APIs, company lists for Discovery APIs, etc.).
For Workflow APIs (Company Research, Industry Research, etc.), results are retrieved via the Download Report endpoint using the report_id, and can be exported as PDF, DOCX, PPT, or JSON.

Complete End-to-End Example

The following Python example shows the full Submit → Poll → Retrieve cycle for a Market Map request:

Cancelling a Request

If you need to abort a job before it completes, you can cancel it using the Request Cancel endpoint, provided the request is still in PENDING or PROCESSING state.

Error Handling

Quick Reference

Next steps: See individual API references for Market Map, Target Screening, Company Enrichment, and Company Deep Intelligence for request-specific parameters and result schemas.