Oracle Retail Merchandising System Python API Docs | dltHub

Build a Oracle Retail Merchandising System-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.

Last updated:

Oracle Retail Merchandising Foundation Cloud Service provides RESTful web services for integrating and managing merchandising data in the cloud. The REST API base URL is https://{rmfcs-host}/RmsMfcsRestServices and All requests require an OAuth 2.0 Bearer token in the Authorization header..

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 add "dlt[hub]" and start loading Oracle Retail Merchandising System data in under 10 minutes.


What data can I load from Oracle Retail Merchandising System?

Here are some of the endpoints you can load from Oracle Retail Merchandising System:

ResourceEndpointMethodData selectorDescription
sales_dataMerchIntegrations/services/sales/itemLocation/weeklyGETitemsRetrieves weekly item location sales data
org_hierarchyMerchIntegrations/services/foundation/orghierGETitemsRetrieves organizational hierarchy records
merch_hierarchy_divisionMerchIntegrations/services/foundation/merchhier/divisionGETitemsRetrieves merchandise hierarchy division records
merch_hierarchy_classMerchIntegrations/services/foundation/merchhier/classGETitemsRetrieves merchandise hierarchy class records
item_detailsMerchIntegrations/services/foundation/omnichannel/itemGETitemsRetrieves item details for omnichannel

How do I authenticate with the Oracle Retail Merchandising System API?

Authentication is performed using OAuth 2.0. Users obtain an access token from the Identity Cloud Service (IDCS) using client credentials and provide it as a Bearer token in the 'Authorization' header.

1. Get your credentials

To obtain credentials for the Oracle Retail Merchandising REST API, you must use OAuth 2.0. 1. Log in to the Oracle Retail Home UI. 2. Navigate to the Administration section (refer to the Retail Home Administration Guide for specific paths). 3. Use the 'Creating OAuth Client Apps' functionality to generate a new OAuth Client. 4. Ensure your user account is assigned the appropriate roles as defined in the Retail Home Integration Guide to allow credential creation. 5. Upon successful creation, securely save the generated Client ID, Client Secret, and the environment-specific Scope. These values are used to request an access token from your IDCS or OCI IAM token URL.

2. Add them to .dlt/secrets.toml

[sources.oracle_retail_merchandising_system_source] client_id = "your_oauth_client_id" client_secret = "your_oauth_client_secret" scope = "your_environment_specific_scope" token_url = "https://<IDCS_BASE_URL>/oauth2/v1/token"

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:

uv init uv add "dlt[hub]"

1. Install the dlt AI harness:

uv run dlthub 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:

uv run dlthub ai toolkit install rest-api-pipeline

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 Oracle Retail Merchandising System 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:

uv run python oracle_retail_merchandising_system_pipeline.py

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

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

Inspect your pipeline and data:

uv run dlthub 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 vDate and items from the Oracle Retail Merchandising System API into DuckDB. It mirrors the endpoint and data selector configuration from the table above:

import dlt from dlt.sources.rest_api import RESTAPIConfig, rest_api_resources @dlt.source def oracle_retail_merchandising_system_source(access_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://{rmfcs-host}/RmsMfcsRestServices", "auth": {"type": "bearer", "token": access_token}, }, "resources": [ {"name": "org_hierarchy", "endpoint": {"path": "MerchIntegrations/services/foundation/orghier", "data_selector": "items"}}, {"name": "sales_data", "endpoint": {"path": "MerchIntegrations/services/sales/itemLocation/weekly", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="oracle_retail_merchandising_system_pipeline", destination="duckdb", dataset_name="oracle_retail_merchandising_system_data", ) load_info = pipeline.run(oracle_retail_merchandising_system_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):

import dlt data = dlt.pipeline("oracle_retail_merchandising_system_pipeline").dataset() sessions_df = data.orghier.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM oracle_retail_merchandising_system_data.orghier LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("oracle_retail_merchandising_system_pipeline").dataset() data.orghier.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 Oracle Retail Merchandising System data to?

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

DestinationExample value
DuckDB (local, default)"duckdb"
PostgreSQL"postgres"
BigQuery"bigquery"
Snowflake"snowflake"
Redshift"redshift"
Databricks"databricks"
Filesystem (S3, GCS, Azure)"filesystem"

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

  • data-exploration — Build custom notebooks, charts, and dashboards for deeper analysis with marimo notebooks.
  • dlthub-platform — Deploy, schedule, and monitor your pipeline in production.
uv run dlthub ai toolkit install data-exploration uv run dlthub ai toolkit install dlthub-platform

Was this page helpful?

Community Hub

Need more dlt context for Oracle Retail Merchandising System?

Request dlt skills, commands, AGENT.md files, and AI-native context.