SurveyCTO Python API Docs | dltHub
Build a SurveyCTO-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
SurveyCTO is a mobile data collection platform that provides a REST API for exporting form data. The REST API base URL is https://{your_server}.surveycto.com/api and SurveyCTO API uses HTTP Basic authentication (username and password)..
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 SurveyCTO data in under 10 minutes.
What data can I load from SurveyCTO?
Here are some of the endpoints you can load from SurveyCTO:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| forms_data_wide_json | /api/v2/forms/data/wide/json/{formId} | GET | Returns submissions for a form in wide JSON format (top‑level array). | |
| forms_files_csv | /api/v1/forms/files/csv/{formId} | GET | N/A | Downloads a CSV export of the form data. |
| forms_list | /api/v2/forms | GET | data | Lists all forms on the server; response wrapped in a data array. |
| form_details | /api/v2/forms/{formId} | GET | Retrieves metadata for a specific form (single JSON object). | |
| form_export_status | /api/v2/forms/data/wide/json/{formId}/status | GET | status | Provides status information about a pending export job. |
How do I authenticate with the SurveyCTO API?
Send an Authorization: Basic <base64‑encoded-username:password> header with each request.
1. Get your credentials
- Log in to SurveyCTO with an admin or privileged user.
- Navigate to User Settings → Roles & Permissions.
- Locate the user that will call the API and edit the role.
- Enable the Allow server API access toggle.
- Save the changes. The username and password of that user are now the API credentials to be used with HTTP Basic authentication.
2. Add them to .dlt/secrets.toml
[sources.surveycto_data_source] username = "your_surveycto_username" password = "your_surveycto_password"
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 SurveyCTO 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 surveycto_data_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline surveycto_data_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset surveycto_data_data The duckdb destination used duckdb:/surveycto_data.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline surveycto_data_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_data_wide_json and forms_files_csv from the SurveyCTO 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 surveycto_data_source(username=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{your_server}.surveycto.com/api", "auth": { "type": "http_basic", "username": username, }, }, "resources": [ {"name": "forms_data_wide_json", "endpoint": {"path": "api/v2/forms/data/wide/json/{formId}"}}, {"name": "forms_files_csv", "endpoint": {"path": "api/v1/forms/files/csv/{formId}"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="surveycto_data_pipeline", destination="duckdb", dataset_name="surveycto_data_data", ) load_info = pipeline.run(surveycto_data_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("surveycto_data_pipeline").dataset() sessions_df = data.forms_data_wide_json.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM surveycto_data_data.forms_data_wide_json LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("surveycto_data_pipeline").dataset() data.forms_data_wide_json.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 SurveyCTO 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 errors
- 401 Unauthorized / 403 Forbidden – Occur when the username/password are incorrect or the user does not have Allow server API access enabled. Verify credentials and permission flag.
Rate limiting
- SurveyCTO may throttle requests. If you receive a 429 Too Many Requests response, pause and retry after the period indicated in the
Retry-Afterheader.
Pagination
- Large data exports use
startandlimitquery parameters. Omit them to retrieve the first page. Continue requesting subsequent pages by incrementingstartuntil the returned array is empty.
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 SurveyCTO?
Request dlt skills, commands, AGENT.md files, and AI-native context.