Load Workday strategic sourcing data in Python using dltHub

Build a Workday strategic sourcing-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.

In this guide, we'll set up a complete Workday Spend data pipeline from API credentials to your first data load in just 10 minutes. You'll end up with a fully declarative Python pipeline based on dlt's REST API connector, like in the partial example code below:

Example code
@dlt.source
def workday_strategic_sourcing_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://api.us.workdayspend.com/services/spend_categories/v1/",
            "auth": {
                "type": "bearer",
                "token": access_token,
            },
        },
        "resources": [
            "events",
            "event_templates",
            "bids"
            ],
    }
    [...]
    yield from rest_api_resources(config)


def get_data() -> None:
    # Connect to destination
    pipeline = dlt.pipeline(
        pipeline_name='workday_strategic_sourcing_pipeline',
        destination='duckdb',
        dataset_name='workday_strategic_sourcing_data', 
    )
    # Load the data
    load_info = pipeline.run(workday_strategic_sourcing_source())
    print(load_info)

Why use dltHub Workspace with LLM Context to generate Python pipelines?

  • Accelerate pipeline development with AI-native context
  • Debug pipelines, validate schemas and data with the integrated Pipeline Dashboard
  • Build Python notebooks for end users of your data
  • Low maintenance thanks to Schema evolution with type inference, resilience and self documenting REST API connectors. A shallow learning curve makes the pipeline easy to extend by any team member
  • dlt is the tool of choice for Pythonic Iceberg Lakehouses, bringing mature data loading loading to pythonic Iceberg with or without catalogs

What you’ll do

We’ll show you how to generate a readable and easily maintainable Python script that fetches data from workday_strategic_sourcing’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:

  • Events: Manage and retrieve event-related data.
  • Event Templates: Access and manage templates for events.
  • Bids: Retrieve bids associated with specific events.
  • Awards: Access information related to awards in the system.
  • Suppliers: Manage and retrieve supplier-related data.

You will then debug the Workday Spend pipeline using our Pipeline Dashboard tool to ensure it is copying the data correctly, before building a Notebook to explore your data and build reports.

Setup & steps to follow

💡
Before getting started, let's make sure Cursor is set up correctly:

Now you're ready to get started!

  1. ⚙️ Set up dlt Workspace

    Install dlt with duckdb support:

    pip install dlt[workspace]

    Initialize a dlt pipeline with Workday Spend support.

    dlt init dlthub:workday_strategic_sourcing duckdb

    The init command will setup the necessary files and folders for the next step.

  2. 🤠 Start LLM-assisted coding

    Here’s a prompt to get you started:

    Prompt
    Please generate a REST API Source for Workday Spend API, as specified in @workday_strategic_sourcing-docs.yaml 
Start with endpoints "events" and "event_templates" and skip incremental loading for now. 
Place the code in workday_strategic_sourcing_pipeline.py and name the pipeline workday_strategic_sourcing_pipeline. 
If the file exists, use it as a starting point. 
Do not add or modify any other files. 
Use @dlt rest api as a tutorial. 
After adding the endpoints, allow the user to run the pipeline with python workday_strategic_sourcing_pipeline.py and await further instructions.

  3. 🔒 Set up credentials

    Authorization requires an API key, user token, and user email in the headers for each request. All requests must be made over HTTPS.

    To get the appropriate API keys, please visit the original source at https://www.workday.com/. If you want to protect your environment secrets in a production environment, look into setting up credentials with dlt.

  4. 🏃‍♀️ Run the pipeline in the Python terminal in Cursor

    python workday_strategic_sourcing_pipeline.py

    If your pipeline runs correctly, you’ll see something like the following:

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

  5. 📈 Debug your pipeline and data with the Pipeline Dashboard

    Now that you have a running pipeline, you need to make sure it’s correct, so you do not introduce silent failures like misconfigured pagination or incremental loading errors. By launching the dlt Workspace Pipeline Dashboard, you can see various information about the pipeline to enable you to test it. Here you can see:

    • Pipeline overview: State, load metrics
    • Data’s schema: tables, columns, types, hints
    • You can query the data itself
    dlt pipeline workday_strategic_sourcing_pipeline show --dashboard

  6. 🐍 Build a Notebook with data explorations and reports

    With the pipeline and data partially validated, you can continue with custom data explorations and reports. To get started, paste the snippet below into a new marimo Notebook and ask your LLM to go from there. Jupyter Notebooks and regular Python scripts are supported as well.

    import dlt

data = dlt.pipeline("workday_strategic_sourcing_pipeline").dataset()
# get "events" table as Pandas frame
data.events.df().head()

Running into errors?

Ensure that the API key, user token, and user email are included in the headers of all requests. Be aware of the rate limit of 5 requests per second, and requests exceeding this limit will return a 429 status. Additionally, all API requests must be made over HTTPS, as HTTP requests will fail. Authentication errors will return a 403 status if the user does not have SSO configured.

Extra resources:

Next steps