Arkose Labs Python API Docs | dltHub

Arkose Labs Verify API is a service that verifies user sessions after bot detection challenges. The REST API base URL is https://verify-api.arkoselabs.com/api/v4 and All requests require a private_key field in the JSON payload for authentication..

dlt is an open-source Python library that handles authentication, pagination, and schema evolution automatically. dlthub provides AI context files that enable code assistants to generate production-ready pipelines. Install with uv pip install "dlt[workspace]" and start loading Arkose Labs data in under 10 minutes.

---

What data can I load from Arkose Labs?

Here are some of the endpoints you can load from Arkose Labs:

---

How do I authenticate with the Arkose Labs API?

Authentication is performed by sending the private_key in the JSON request body; no additional headers are required.

1. Get your credentials

1. Log in to the Arkose Labs dashboard.
2. Navigate to Integrations → API Keys.
3. Click Create New Key or locate the existing Private Key for Verify API.
4. Copy the private_key value and store it securely for use in API requests.

2. Add them to .dlt/secrets.toml

Copy
[sources.arkose_labs_source]
api_key = "your_private_key_here"

dlt reads this automatically at runtime — never hardcode tokens in your pipeline script. For production environments, see setting up credentials with dlt for environment variable and vault-based options.

---

How do I set up and run the pipeline?

Set up a virtual environment and install dlt:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
dlt ai init --agent <your-agent> # <agent>: claude | cursor | codex

This installs project rules, a secrets management skill, appropriate ignore files, and configures the dlt MCP server for your agent. Learn more →

2. Install the rest-api-pipeline toolkit:

Copy
dlt ai toolkit rest-api-pipeline install

This loads the skills and context about dlt the agent uses to build the pipeline iteratively, efficiently, and safely. The agent uses MCP tools to inspect credentials — it never needs to read your secrets.toml directly. Learn more →

3. Start LLM-assisted coding:

Use /find-source to load data from the Arkose Labs API into DuckDB.

The rest-api-pipeline toolkit takes over from here — it reads relevant API documentation, presents you with options for which endpoints to load, and follows a structured workflow to scaffold, debug, and validate the pipeline step by step.

4. Run the pipeline:

Copy
python arkose_labs_pipeline.py

If everything is configured correctly, you'll see output like this:

Copy
Pipeline arkose_labs_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset arkose_labs_data
The duckdb destination used duckdb:/arkose_labs.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
dlt pipeline arkose_labs_pipeline show

This opens the Pipeline Dashboard where you can verify pipeline state, load metrics, schema (tables, columns, types), and query the loaded data directly.

---

Python pipeline example

This example loads request_schema and response_schema from the Arkose Labs API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

Copy
import dlt
from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources

@dlt.source
def arkose_labs_source(private_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://verify-api.arkoselabs.com/api/v4",
            "auth": {
                "type": "api_key",
                "api_key": private_key,
            },
        },
        "resources": [
            {"name": "request_schema", "endpoint": {"path": "schema/request"}},
            {"name": "response_schema", "endpoint": {"path": "schema/response"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="arkose_labs_pipeline",
        destination="duckdb",
        dataset_name="arkose_labs_data",
    )
    load_info = pipeline.run(arkose_labs_source())
    print(load_info)

To add more endpoints, append entries from the resource table to the "resources" list using the same name, path, and data_selector pattern.

---

How do I query the loaded data?

Once the pipeline runs, dlt creates one table per resource. You can query with Python or SQL.

Python (pandas DataFrame):

Copy
import dlt

data = dlt.pipeline("arkose_labs_pipeline").dataset()
sessions_df = data.verify.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM arkose_labs_data.verify LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("arkose_labs_pipeline").dataset()
data.verify.df().head()

See how to explore your data in marimo Notebooks and how to query your data in Python with dataset.

---

What destinations can I load Arkose Labs data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication Errors

• Missing or invalid private_key: The API returns an error object, e.g., { "error": "DENIED ACCESS" }. Ensure the private_key is correct and included in the request body.

Validation Errors

• Missing required fields: If session_token or other required fields are omitted, the response contains an error message indicating the missing parameter.

Rate Limiting

• The documentation does not specify a rate‑limit header, but Arkose Labs may enforce request throttling. If you receive HTTP 429 responses, back‑off and retry with exponential delays.

Unexpected Payload Structure

• The response schema may change; validate responses against the /schema/response endpoint to catch structural changes early.

Ensure that the API key is valid to avoid 401 Unauthorized errors. Also, verify endpoint paths and parameters to avoid 404 Not Found errors.

---

Next steps

Continue your data engineering journey with the other toolkits of the dltHub AI Workbench:

• data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
• dlthub-runtime — Deploy, schedule, and monitor your pipeline in production.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack