Fancyhands Python API Docs | dltHub
Build a Fancyhands-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
Fancy Hands is a virtual assistant platform that exposes a developer API to create tasks, manage incoming-call phone numbers and conversations, and integrate assistant-driven workflows. The REST API base URL is https://www.fancyhands.com/api and API access requires a consumer key and secret (API key pair) provided in the API Explorer / developer dashboard..
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 Fancyhands data in under 10 minutes.
What data can I load from Fancyhands?
Here are some of the endpoints you can load from Fancyhands:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| incoming_call_numbers | /call/number | GET | Search available phone numbers and buy a number (Incoming Calls API Numbers endpoint) | |
| incoming_call_objects | /call/incoming | GET | List Incoming Call Objects (Incoming Calls API Incoming endpoint) | |
| incoming_call_history | /call/history | GET | Retrieve history of incoming calls (Incoming Calls API History endpoint) | |
| api_explorer | /explorer | GET | Interactive API Explorer / dashboard showing keys and app settings | |
| developer_info | /developer | GET | Developer overview and links to docs, examples and github |
How do I authenticate with the Fancyhands API?
Fancy Hands issues an API consumer key and secret for apps. Requests use those credentials from your app context; the public docs instruct developers to email api@fancyhands.com to get started and obtain the keys.
1. Get your credentials
- Email api@fancyhands.com describing your use case to request API access.
- The Fancy Hands team will create an app and supply a consumer key and secret (visible in the API Explorer).
- Use the provided key/secret in the API Explorer or your app; configure a webhook URL if needed.
2. Add them to .dlt/secrets.toml
[sources.fancyhands_source] consumer_key = "your_consumer_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:
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 Fancyhands 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 fancyhands_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline fancyhands_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset fancyhands_data The duckdb destination used duckdb:/fancyhands.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline fancyhands_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 incoming_call_numbers and incoming_call_objects from the Fancyhands 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 fancyhands_source(consumer_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://www.fancyhands.com/api", "auth": { "type": "api_key", "consumer_key": consumer_key, }, }, "resources": [ {"name": "incoming_call_numbers", "endpoint": {"path": "call/number"}}, {"name": "incoming_call_objects", "endpoint": {"path": "call/incoming"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="fancyhands_pipeline", destination="duckdb", dataset_name="fancyhands_data", ) load_info = pipeline.run(fancyhands_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("fancyhands_pipeline").dataset() sessions_df = data.incoming_call_numbers.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM fancyhands_data.incoming_call_numbers LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("fancyhands_pipeline").dataset() data.incoming_call_numbers.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 Fancyhands 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 have not been issued a consumer key/secret by Fancy Hands (contact api@fancyhands.com) the API Explorer will show you as not logged in and requests will fail. Ensure you use the app consumer key/secret shown in the API Explorer.
Webhook delivery and retries
When configuring webhooks in the API Explorer, Fancy Hands will POST to the webhook and will retry up to 3 times on delivery failure.
Buying phone numbers, billing and errors
Buying a phone number incurs a monthly fee (the price is returned by the Number endpoint). Ensure your account has credits; the Explorer shows credits remaining. If purchase fails, inspect error response from the Number POST for details.
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 Fancyhands?
Request dlt skills, commands, AGENT.md files, and AI-native context.