Videoask Python API Docs | dltHub
Build a Videoask-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
VideoAsk is a platform for creating video‑first forms (videoasks) to collect video or text responses from respondents. The REST API base URL is https://api.videoask.com and All requests require OAuth2 Bearer tokens or temporary API tokens for testing..
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 Videoask data in under 10 minutes.
What data can I load from Videoask?
Here are some of the endpoints you can load from Videoask:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| organizations | /organizations | GET | Retrieve organization metadata | |
| forms | /forms | GET | List videoasks (forms) | |
| questions | /forms/{form_id}/questions | GET | List questions for a form | |
| answers | /questions/{question_id}/answers | GET | List answers for a question (paginated) | |
| responses | /responses | GET | List responses/submissions | |
| respondents | /respondents | GET | List respondents | |
| media | /media | GET | List uploaded media assets | |
| webhooks | /webhooks | GET | Manage/list webhooks |
How do I authenticate with the Videoask API?
VideoAsk uses OAuth2 (authorization code flow) for production and accepts a temporary Bearer token for testing; send it in the header Authorization: Bearer <token>.
1. Get your credentials
- Log in to https://app.videoask.com/app.
- Go to Account > API and click Copy code to obtain a temporary token for testing.
- For production, open Organization Settings > Developer Apps and click Create a developer app.
- Save the generated client_id and client_secret.
- Implement the OAuth2 authorization code flow: direct the user to https://auth.videoask.com/authorize, then exchange the returned code at POST https://api.videoask.com/oauth/token to receive access and refresh tokens.
2. Add them to .dlt/secrets.toml
[sources.videoask_source] api_key = "your_bearer_token_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:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
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:
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 Videoask 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:
python videoask_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline videoask_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset videoask_data The duckdb destination used duckdb:/videoask.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline videoask_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 forms and responses from the Videoask API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:
import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def videoask_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.videoask.com", "auth": { "type": "bearer", "token": api_key, }, }, "resources": [ {"name": "forms", "endpoint": {"path": "forms"}}, {"name": "responses", "endpoint": {"path": "responses"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="videoask_pipeline", destination="duckdb", dataset_name="videoask_data", ) load_info = pipeline.run(videoask_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):
import dlt data = dlt.pipeline("videoask_pipeline").dataset() sessions_df = data.responses.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM videoask_data.responses LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("videoask_pipeline").dataset() data.responses.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 Videoask data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example value |
|---|---|
| DuckDB (local, default) | "duckdb" |
| PostgreSQL | "postgres" |
| BigQuery | "bigquery" |
| Snowflake | "snowflake" |
| Redshift | "redshift" |
| Databricks | "databricks" |
| Filesystem (S3, GCS, Azure) | "filesystem" |
Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.
Troubleshooting
Authentication failures
If you see 401 Unauthorized, verify you are sending Authorization: Bearer <token>. Temporary tokens from Account > API expire; for production use oauth tokens obtained via the client_id/client_secret flow.
Pagination and missing count
Several listing endpoints are paginated (examples: /forms, /questions/{id}/answers, /messages). Send limit and/or offset query params. The API will stop including a top‑level count by default; include with_count=1 if you need the total.
Rate limits and 429 errors
If the API returns 429 Too Many Requests, back off and retry after the period indicated in Retry-After header.
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.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Videoask?
Request dlt skills, commands, AGENT.md files, and AI-native context.