No logo available for Free Url Shortener to DuckDB connector icon

Load Free Url Shortener data to DuckDB

Build a Free Url Shortener to DuckDB pipeline with your coding agent. One prompt scaffolds it with the dltHub AI harness, plus the Free Url Shortener API base URL, auth, endpoints, and incremental loading.

SourceFree Url ShortenerFree Url Shortener API DocumentationDestinationDuckDBIn-process analytical database. The default local destination for dlt pipelines.

Ulvis is a free URL shortener service that provides a public REST API for programmatic link management. Everything needed to build a working Free Url Shortener → DuckDB pipeline is on this page: the API's base URL, authentication, endpoints, pagination and incremental field — plus a prompt that hands the whole job to your coding agent.


Build your Free Url Shortener to DuckDB pipeline

Paste this prompt into Claude, Codex, or Cursor. The agent does the rest.

Prompt
Run uvx dlthub-init@latest to build a pipeline from Free Url Shortener to DuckDB and run it on dltHub

That scaffolds a dltHub workspace and installs the dltHub AI harness — the project rules, the secrets-management skill, and the dlt MCP server your agent needs to work safely. From there it reads the Free Url Shortener API, proposes the endpoints to load, then writes, runs and validates the pipeline while you review rather than type. Credentials are inspected through MCP tools, so your agent never reads secrets.toml itself. How the LLM-native workflow works →

Prefer to write it yourself? Every fact the agent uses is below.


Free Url Shortener API at a glance

Base URLhttps://ulvis.net
Example endpointGET v1/links
Authenticationno authentication required — sent in the Authorization header, prefixed Bearer
PaginationPage-number via search_after, page size via limit
Incremental fieldlast
Record idid
API referencehttps://shorten.dev/docs

These values come from the Free Url Shortener API reference — the authoritative source if anything here looks out of date.


How do I authenticate with the Free Url Shortener API?

The API does not require authentication; it is a public service.

1. Get your credentials

To obtain an API token for the TinyURL REST API, log in to your account at the TinyURL dashboard, navigate to Profile > API, enter a name for your token, select the required permissions (e.g., 'create', 'update'), and click 'Create Token'. Copy the token immediately, as it will not be displayed again.

2. Add them to .dlt/secrets.toml

[sources.free_url_shortener_source] api_token = "your_tinyurl_api_token_here"

dlt reads this file automatically at runtime. With the harness, the setup-secrets skill prompts you for the values and never handles the raw credential in chat. For production, see setting up credentials with dlt.


What Free Url Shortener data can I load into DuckDB?

These are the Free Url Shortener endpoints dlt can load into DuckDB:

ResourceEndpointMethodData selectorDescription
links/v1/linksGETList branded short links
domains/v1/domainsGETList branded domains
links/api/linksGETlinksList short links for an account or domain
domains/api/domainsGETdomainsList domains available in the account
tags/api/tagsGETtagsList tags associated with links

How do I load only new Free Url Shortener records?

Free Url Shortener exposes last on v1/links, so dlt can request only the records that changed since the last run. Set it as the cursor_path and dlt tracks the high-water mark for you between runs.

{"name": "rebrandly_links", "endpoint": { "path": "v1/links", "incremental": {"cursor_path": "last", "initial_value": "2024-01-01T00:00:00Z"}, }}

On the first run dlt loads everything from initial_value; on every run after that it requests only what changed and appends with write_disposition="merge" if you set a primary key. See incremental loading.


What does the generated Free Url Shortener pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /create and /analytics from the Free Url Shortener API into DuckDB:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def free_url_shortener_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://ulvis.net", "auth": {"type": "bearer", "token": api_key}, }, "resources": [ {"name": "rebrandly_links", "endpoint": {"path": "v1/links"}}, {"name": "short_io_links", "endpoint": {"path": "api/links", "data_selector": "links"}} ], } yield from rest_api_resources(config) def load_free_url_shortener_to_duckdb() -> None: pipeline = dlt.pipeline( pipeline_name="free_url_shortener_pipeline", destination="duckdb", dataset_name="free_url_shortener_data", ) load_info = pipeline.run(free_url_shortener_source()) print(load_info) if __name__ == "__main__": load_free_url_shortener_to_duckdb()

Run it with python free_url_shortener_pipeline.py. The agent iterates on this until it loads cleanly — you review and approve, rather than write it from scratch.


How do I query Free Url Shortener data in DuckDB?

dlt creates one table per resource. Query the loaded data with Python or SQL — or ask your agent to, through the MCP server's execute_sql_query tool.

Python (pandas DataFrame):

import dlt data = dlt.pipeline("free_url_shortener_pipeline").dataset() df = data.links.df() print(df.head())

SQL:

SELECT * FROM free_url_shortener_data.links LIMIT 10;

See querying your data with dataset and exploring it in marimo notebooks.


How do I deploy the Free Url Shortener to DuckDB pipeline in production?

The pipeline runs locally, which is ideal for prototyping and one-off analysis. When you need it on a schedule, monitored on every load, and shared with your team, deploy the same dlt code on the dltHub platform — no infrastructure to maintain. The prompt above already ends with "run it on dltHub", so your agent can take it there directly.

  • Deploy & schedule — run the pipeline as a managed job with automatic retries.
  • Monitor — observable job queues, alerting, and load metrics for every run.
  • Transform — promote raw Free Url Shortener loads into governed, documented models.
  • Visualize & share — explore data in notebooks and publish live dashboards instead of static screenshots.

Book a demo →


What other destinations can I load Free Url Shortener data to?

dlt loads into any of these — only the destination argument changes:

DestinationExample value
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

Set dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. On the dltHub platform the same pipeline runs against a managed Iceberg lakehouse. See the full destinations list.


Next steps

Was this page helpful?

Community Hub

Need more dlt context for Free Url Shortener to DuckDB?

Request dlt skills, commands, AGENT.md files, and AI-native context.