Load Nice Expert Help data to DuckDB

Nice Expert Help is the CXone Mpower Expert REST API for programmatic access to site content, users, analytics, and integrations. Everything needed to build a working Nice Expert Help → 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 Nice Expert Help 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 Nice Expert Help 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 Nice Expert Help 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.

---

Nice Expert Help API at a glance

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

---

How do I authenticate with the Nice Expert Help API?

All API requests require an API token supplied via the 'X-Deki-Token' header.

1. Get your credentials

1. Log in to your CXone instance and navigate to the Admin application. 2. Select the specific account or user for which you need to create an integration. 3. Navigate to the Access Keys tab. 4. Click 'Generate New Access Key'. 5. Copy the 'Access Key ID' and the 'Secret Access Key'. Note: The secret key is shown only once; ensure you save it securely immediately, as you will need to create a new key if it is lost. 6. If your integration requires OAuth2 application registration, ensure your application is registered via the DEVone Developer Community to obtain your 'Client ID' and 'Client Secret'.

2. Add them to .dlt/secrets.toml

Copy
[sources.nice_expert_help_source]
deki_token = "REPLACE_ME"

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 Nice Expert Help data can I load into DuckDB?

These are the Nice Expert Help endpoints dlt can load into DuckDB:

---

How do I load only new Nice Expert Help records?

The Nice Expert Help 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": "site_query", "endpoint": {
    "path": "/@api/deki/site/query",
    # 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 Nice Expert Help pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /auth/authorize and /auth/token from the Nice Expert Help API into DuckDB:

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

@dlt.source
def nice_expert_help_source(deki_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://{hostname}/@api/deki",
            "auth": {"type": "api_key", "api_key": deki_token, "name": "X-Deki-Token", "location": "header"},
        },
        "resources": [
            {"name": "site_query", "endpoint": {"path": "/@api/deki/site/query"}},
            {"name": "site_jobs", "endpoint": {"path": "/@api/deki/site/jobs"}}
        ],
    }
    yield from rest_api_resources(config)


def load_nice_expert_help_to_duckdb() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="nice_expert_help_pipeline",
        destination="duckdb",
        dataset_name="nice_expert_help_data",
    )
    load_info = pipeline.run(nice_expert_help_source())
    print(load_info)


if __name__ == "__main__":
    load_nice_expert_help_to_duckdb()

Run it with python nice_expert_help_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 Nice Expert Help 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("nice_expert_help_pipeline").dataset()
df = data.site_query.df()
print(df.head())

SQL:

Copy
SELECT * FROM nice_expert_help_data.site_query LIMIT 10;

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

---

How do I deploy the Nice Expert Help 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 Nice Expert Help 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 Nice Expert Help 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