Texas Instruments Python API Docs | dltHub

Texas Instruments offers REST APIs for product information and store management, requiring authentication and providing JSON responses for product details and order processing. The REST API base URL is https://transact.ti.com/v1 and All requests require OAuth 2.0 client credentials: exchange client_id and client_secret for a Bearer access token, then include Authorization: Bearer {access_token} on requests..

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

---

What data can I load from Texas Instruments?

Here are some of the endpoints you can load from Texas Instruments:

---

How do I authenticate with the Texas Instruments API?

Obtain an API client key (client_id) and secret from your myTI company account via the API Keys / Keys and Access page. Use the token endpoint POST https://transact.ti.com/v1/oauth/accesstoken with Content-Type: application/x-www-form-urlencoded and grant_type=client_credentials, client_id and client_secret to receive an access token. Include header Authorization: Bearer {access_token} on subsequent API calls.

1. Get your credentials

1. Create or use an existing myTI company account. 2. Request API access via the "API Keys and Access" page for the Product Information API suite (or Store API for ordering/inventory). 3. Once approved, note your client key (client_id) and client secret. 4. Exchange client_id and client_secret for an access token at https://transact.ti.com/v1/oauth/accesstoken using grant_type=client_credentials. 5. Use Authorization: Bearer {access_token} in all API requests.

2. Add them to .dlt/secrets.toml

Copy
[sources.texas_instruments_product_info_source]
client_id = "your_client_id"
client_secret = "your_client_secret"

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 Texas Instruments 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 texas_instruments_product_info_pipeline.py

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

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

Inspect your pipeline and data:

Copy
dlt pipeline texas_instruments_product_info_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 products and products_extended from the Texas Instruments 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 texas_instruments_product_info_source(client_secret=dlt.secrets.value):
    config: RESTAPIConfig = {
        "client": {
            "base_url": "https://transact.ti.com/v1",
            "auth": {
                "type": "bearer",
                "token": client_secret,
            },
        },
        "resources": [
            {"name": "products", "endpoint": {"path": "products/{part_number}"}},
            {"name": "products_extended", "endpoint": {"path": "products-extended/{part_number}", "data_selector": "Product"}}
        ],
    }
    yield from rest_api_resources(config)


def get_data() -> None:
    pipeline = dlt.pipeline(
        pipeline_name="texas_instruments_product_info_pipeline",
        destination="duckdb",
        dataset_name="texas_instruments_product_info_data",
    )
    load_info = pipeline.run(texas_instruments_product_info_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("texas_instruments_product_info_pipeline").dataset()
sessions_df = data.products.df()
print(sessions_df.head())

SQL (DuckDB example):

Copy
SELECT * FROM texas_instruments_product_info_data.products LIMIT 10;

In a marimo or Jupyter notebook:

Copy
import dlt

data = dlt.pipeline("texas_instruments_product_info_pipeline").dataset()
data.products.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 Texas Instruments 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.

---

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