Concord Python API Docs | dltHub

Concord is a REST API for managing workflows, processes and organizations (Concord: workflow orchestration; ConcordNow: contract lifecycle management API). The REST API base URL is https://concord.walmartlabs.com (Walmart Concord; API path prefixes: /api/v1 and /api/v2) and ConcordNow docs show a UAT base: https://uat.concordnow.com/api/rest/1 (many example paths use this base). and API key authentication required (header-based)..

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 Concord data in under 10 minutes.

---

What data can I load from Concord?

Here are some of the endpoints you can load from Concord:

---

How do I authenticate with the Concord API?

Provide an API Key in the request header. Walmart Concord docs indicate using the Authorization header with the API key; ConcordNow uses X-API-KEY header. Include Content-Type for JSON requests when applicable.

1. Get your credentials

Log into your Concord (or ConcordNow) account -> navigate to API Keys / Integrations -> create/generate a new API key -> copy the key and store it securely. For Walmart Concord create via POST /api/v1/apikey (docs show API key management endpoints).

2. Add them to .dlt/secrets.toml

Copy
[sources.concord_contract_management_source]
api_key = "your_api_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:

Copy
uv venv && source .venv/bin/activate
uv pip install "dlt[workspace]"

1. Install the dlt AI Workbench:

Copy
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:

Copy
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 Concord 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:

Copy
python concord_contract_management_pipeline.py

If everything is configured correctly, you'll see output like this:

Copy
Pipeline concord_contract_management_pipeline load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset concord_contract_management_data
The duckdb destination used duckdb:/concord_contract_management.duckdb location to store data
Load package 1749667187.541553 is LOADED and contains no failed jobs

Inspect your pipeline and data:

Copy
dlt pipeline concord_contract_management_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 process_list and orgs from the Concord API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

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

@dlt.source
def concord_contract_management_source(api_key=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://concord.walmartlabs.com (Walmart Concord; API path prefixes: /api/v1 and /api/v2) and ConcordNow docs show a UAT base: https://uat.concordnow.com/api/rest/1 (many example paths use this base).",
            "auth": {
                "type": "api_key",
                "api_key": api_key,
            },
        },
        "resources": [
            {"name": "process_list", "endpoint": {"path": "api/v2/process"}},
            {"name": "organizations", "endpoint": {"path": "user/me/organizations", "data_selector": "organizations"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="concord_contract_management_pipeline",
        destination="duckdb",
        dataset_name="concord_contract_management_data",
    )
    load_info = pipeline.run(concord_contract_management_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):

Copy
import dlt

data = dlt.pipeline("concord_contract_management_pipeline").dataset()
sessions_df = data.process_list.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM concord_contract_management_data.process_list LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("concord_contract_management_pipeline").dataset()
data.process_list.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 Concord data to?

dlt supports loading into any of these destinations — only the destination parameter changes:

Change the destination in dlt.pipeline(destination="snowflake") and add credentials in .dlt/secrets.toml. See the full destinations list.

---

Troubleshooting

Authentication failures

401 Unauthorized returned when API key header is missing or invalid. For ConcordNow include X-API-KEY header; for Walmart Concord use Authorization header with the API key (or the API key mechanisms described in /api/v1/apikey docs).

Rate limits and 4xx/5xx

API returns standard HTTP status codes. 4xx indicates client errors (400,401,403,404,409); 5xx indicates server errors (500,502,503,504). ConcordNow docs list these codes and indicate error objects in JSON responses.

Pagination and selectors

Many ConcordNow list endpoints return paginated objects with keys such as items, reports, attachments, groups, tags, members, organizations. Use the documented response keys (e.g. "items", "attachments", "members", "organizations", "reports", "groups", "tags") as the data selector when extracting arrays. Some Walmart Concord endpoints (process endpoints) return process objects or top-level arrays but the docs do not always show a named array key  check the actual environment response for v2/process in your Concord installation.

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.

Copy
dlt ai toolkit data-exploration install
dlt ai toolkit dlthub-runtime install

• How to deploy a pipeline
• How to explore your data in marimo Notebooks
• How to query your data in Python with dataset
• Join the dlt community on Slack