Skip to main content
Every Data Hub capability is exposed through one public REST API. The web portal, MCP, and the Python and JavaScript client libraries are different ways to call the same data and the same billing rules.

REST API

Base URL https://api-datahub.octoparse.com. Every endpoint starts with /v1. Requests and responses are JSON. Authenticated endpoints use Authorization: Bearer <API Key>. Create an API key in the Octoparse account center. Start a run and wait for the result:

API reference

Shared conventions for auth, response shape, pagination, and errors, plus every endpoint by resource.

OpenAPI spec

Machine-readable contract you can import into Postman, codegen tools, or AI coding assistants.

Client libraries

The official client libraries wrap every caller-facing REST endpoint. Methods map one-to-one to endpoints and return the raw data payload from the response.
Python client library docs

MCP

To let an agent use Data Apps without writing code, connect the Data Hub general MCP. It exposes seven tools for search, detail, run, status, result, cancel, and list, and can pin a specific app as a dedicated tool. See Data Hub MCP capabilities and the general connection guide.

For AI

  • Full-site index: https://www.octoparse.com/docs/llms.txt
  • Append .md to any docs URL to fetch the Markdown source.
  • Contract-authoring skill: GET /v1/skills/dataapp-contract-json.zip for Claude Code, Codex, and similar assistants that generate Data App contracts.