Load Azure Translator data in Python using dltHub

Build a Azure Translator-to-database or-dataframe pipeline in Python using dlt with automatic Cursor support.

In this guide, we'll set up a complete Microsoft Translator 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 microsoft_translator_migration_source(access_token=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://{document-translation-endpoint}/",
            "auth": {
                "type": "bearer",
                "token": access_token,
            },
        },
        "resources": [
            feature-flags,,translator/document,,document/batches
            ],
    }
    [...]
    yield from rest_api_resources(config)


def get_data() -> None:
    # Connect to destination
    pipeline = dlt.pipeline(
        pipeline_name='microsoft_translator_migration_pipeline',
        destination='duckdb',
        dataset_name='microsoft_translator_migration_data', 
    )
    # Load the data
    load_info = pipeline.run(microsoft_translator_migration_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 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 microsoft_translator_migration’s API and loads it into Iceberg, DataFrames, files, or a database of your choice. Here are some of the endpoints you can load:

  • Document Translation: Provides features for translating documents in various formats.
  • Feature Flags: Allows management of feature flags for application configuration.
  • Batch Document Translation: Handles the translation of multiple documents in a batch process.

You will then debug the Microsoft Translator 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 Microsoft Translator support.

    dlt init dlthub:microsoft_translator_migration 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 Microsoft Translator API, as specified in @microsoft_translator_migration-docs.yaml 
Start with endpoints feature-flags and  and skip incremental loading for now. 
Place the code in microsoft_translator_migration_pipeline.py and name the pipeline microsoft_translator_migration_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 microsoft_translator_migration_pipeline.py and await further instructions.

  3. 🔒 Set up credentials

    The authentication method employed is via an API key that needs to be included in the request header as 'Ocp-Apim-Subscription-Key'.

    To get the appropriate API keys, please visit the original source at https://www.microsoft.com/en-us/translator/. 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 microsoft_translator_migration_pipeline.py

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

    Pipeline microsoft_translator_migration load step completed in 0.26 seconds
1 load package(s) were loaded to destination duckdb and into dataset microsoft_translator_migration_data
The duckdb destination used duckdb:/microsoft_translator_migration.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 microsoft_translator_migration_pipeline show

  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("microsoft_translator_migration_pipeline").dataset()
# get eature-flag table as Pandas frame
data.eature-flag.df().head()

Running into errors?

It's crucial to manage API keys securely, such as by using Azure Key Vault, and to avoid hardcoding them in your code. Be sure to remove any keys from code after use and refrain from sharing them publicly. Additionally, when using Azure Functions, it's recommended to adopt an isolated worker model.

Extra resources:

Next steps