Load Scoro data to DuckDB

Scoro is a business management platform that offers a REST API for accessing contacts, projects, tasks, invoices, and other resources. Everything needed to build a working Scoro → 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 Scoro to DuckDB pipeline

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

PromptCopy prompt
Run uvx dlthub-init@latest to build a pipeline from Scoro 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 Scoro 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.

---

Scoro API at a glance

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

---

How do I authenticate with the Scoro API?

Authentication is handled by including the apiKey or user_token in the JSON body of an HTTP POST request.

1. Get your credentials

To obtain your Scoro API credentials, follow these steps: 1. Log in to your Scoro account. 2. Navigate to your profile settings by clicking your profile picture and selecting Settings. 3. In the left-hand menu, locate and click on the API section. 4. Click Generate new API key to create a site-wide apiKey. 5. If you require a user-specific token instead, navigate to My Profile → API Tokens to generate a user_token. 6. Copy the generated key/token and note your company_account_id (usually found on the same dashboard), as both are required for API authentication.

2. Add them to .dlt/secrets.toml

Copy
[sources.scoro_source]
api_key = "your_api_key_here"
company_account_id = "your_company_account_id_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 Scoro data can I load into DuckDB?

These are the Scoro endpoints dlt can load into DuckDB:

---

How do I load only new Scoro records?

The Scoro API reference does not document a timestamp or sequence field for these endpoints, so there is nothing to advertise here as verified. Pick a field from the endpoints table above that increases with every write, then set it as the cursor_path.

Copy
{"name": "contacts", "endpoint": {
    "path": "contacts/list",
    # Replace with a field that increases on every write.
    "incremental": {"cursor_path": "REPLACE_ME", "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 Scoro pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading contacts/list and contacts/modify from the Scoro API into DuckDB:

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

@dlt.source
def scoro_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://{subdomain}.scoro.com/api/v2",
            "auth": {"type": "bearer", "token": api_key},
        },
        "resources": [
            {"name": "contacts", "endpoint": {"path": "contacts/list", "data_selector": "data"}},
            {"name": "relations", "endpoint": {"path": "relations", "data_selector": "data"}}
        ],
    }
    yield from rest_api_resources(config)


def load_scoro_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="scoro_pipeline",
        destination="duckdb",
        dataset_name="scoro_data",
    )
    load_info = pipeline.run(scoro_source())
    print(load_info)


if __name__ == "__main__":
    load_scoro_to_duckdb()

Run it with python scoro_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 Scoro 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):

Copy
import dlt

data = dlt.pipeline("scoro_pipeline").dataset()
df = data.contacts.df()
print(df.head())

SQL:

Copy
SELECT * FROM scoro_data.contacts LIMIT 10;

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

---

How do I deploy the Scoro 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 Scoro 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 Scoro data to?

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

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

• Ready for production? Book a demo of the dltHub platform →
• dlt LLM-native workflow docs
• REST API source reference
• Join the dlt community on Slack