Load MarkLogic data to Microsoft Fabric

MarkLogic REST API provides services for document manipulation and management within the MarkLogic Server ecosystem. Everything needed to build a working MarkLogic → Microsoft Fabric 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 MarkLogic to Microsoft Fabric pipeline

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

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 MarkLogic 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.

---

MarkLogic API at a glance

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

---

How do I authenticate with the MarkLogic API?

For OAuth-based authentication, requests require an Authorization header with the format 'Bearer {access_token}'. For standard authentication, username and password are required, typically handled via HTTP Basic or Digest authentication.

1. Get your credentials

To obtain credentials for the MarkLogic REST API: 1. Ensure you have a MarkLogic Server instance installed and running. 2. Log in to the MarkLogic Admin Interface (typically on port 8001 or 8002). 3. Navigate to Security to create or identify a user account (e.g., a user with the 'rest-reader', 'rest-writer', or 'rest-admin' role). 4. Use these username and password credentials for authentication. The MarkLogic REST API natively supports Basic and Digest authentication. If using the MarkLogic cloud offering, you may generate an API key via the cloud provider's developer dashboard.

2. Add them to .dlt/secrets.toml

Copy
[sources.marklogic_source]
username = "your_username"
password = "your_password"
# If using cloud-based bearer token authentication
# access_token = "your_bearer_token"

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 MarkLogic data can I load into Microsoft Fabric?

These are the MarkLogic endpoints dlt can load into Microsoft Fabric:

---

How do I load only new MarkLogic records?

MarkLogic exposes start on v1/search, 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.

Copy
{"name": "search", "endpoint": {
    "path": "v1/search",
    "data_selector": "search",
    "incremental": {"cursor_path": "start", "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 MarkLogic pipeline look like?

A standard dlt REST API pipeline — the same code you would write by hand, loading /v1/rest-apis and /v1/search from the MarkLogic API into Microsoft Fabric:

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

@dlt.source
def marklogic_source(username=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "http://host:port/version/",
            "auth": {"type": "bearer", "token": username},
        },
        "resources": [
            {"name": "search", "endpoint": {"path": "v1/search", "data_selector": "search"}},
            {"name": "values", "endpoint": {"path": "v1/values/{name}", "data_selector": "values"}}
        ],
    }
    yield from rest_api_resources(config)


def load_marklogic_to_fabric() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="marklogic_pipeline",
        destination="fabric",
        dataset_name="marklogic_data",
    )
    load_info = pipeline.run(marklogic_source())
    print(load_info)


if __name__ == "__main__":
    load_marklogic_to_fabric()

Run it with uv run python marklogic_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 MarkLogic data in Microsoft Fabric?

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("marklogic_pipeline").dataset()
df = data.search.df()
print(df.head())

SQL:

Copy
SELECT * FROM marklogic_data.search LIMIT 10;

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

---

How do I deploy the MarkLogic to Microsoft Fabric 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 MarkLogic 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 MarkLogic 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