Oscar Python API Docs | dltHub
Build a Oscar-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.
Last updated:
OSCAR is a platform that provides a secure REST API for managing services in a Kubernetes‑based cloud environment. The REST API base URL is The base URL is the cluster ingress address (e.g., https://<master-node-ip>) and varies per deployment. and All requests require a Bearer token for authentication..
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 Oscar data in under 10 minutes.
What data can I load from Oscar?
Here are some of the endpoints you can load from Oscar:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| services | /services | GET | items | List of managed services |
| users | /users | GET | items | List of users with access |
| projects | /projects | GET | items | Projects available in the cluster |
| sites | /sites | GET | items | Information about cluster sites |
| attributes | /attributes | GET | items | Key‑value attributes for resources |
How do I authenticate with the Oscar API?
Authentication is performed by adding an HTTP header Authorization: Bearer <token> to every request. The token can be an OSCAR service access token or a user Access Token when the cluster is integrated with EGI Check‑in.
1. Get your credentials
- Log into the OSCAR management console (or the EGI Check‑in portal if the cluster is integrated).
- Navigate to the Credentials or Tokens section.
- Create a new service access token or retrieve your personal Access Token.
- Copy the token value for use in the
secrets.tomlfile.
2. Add them to .dlt/secrets.toml
[sources.oscar_source] bearer_token = "your_token_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:
uv venv && source .venv/bin/activate uv pip install "dlt[workspace]"
1. Install the dlt AI Workbench:
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:
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 Oscar 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:
python oscar_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline oscar_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset oscar_data The duckdb destination used duckdb:/oscar.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline oscar_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 services and users from the Oscar 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 oscar_source(bearer_token=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "The base URL is the cluster ingress address (e.g., https://<master-node-ip>) and varies per deployment.", "auth": { "type": "bearer", "token": bearer_token, }, }, "resources": [ {"name": "services", "endpoint": {"path": "services", "data_selector": "items"}}, {"name": "users", "endpoint": {"path": "users", "data_selector": "items"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="oscar_pipeline", destination="duckdb", dataset_name="oscar_data", ) load_info = pipeline.run(oscar_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("oscar_pipeline").dataset() sessions_df = data.services.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM oscar_data.services LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("oscar_pipeline").dataset() data.services.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 Oscar data to?
dlt supports loading into any of these destinations — only the destination parameter changes:
| Destination | Example 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.
Troubleshooting
Authentication Errors
- 401 Unauthorized – Occurs when the Bearer token is missing, expired, or invalid. Ensure the token is correctly set in the
Authorizationheader.
Rate Limiting
- 429 Too Many Requests – The API may throttle excessive calls. Implement exponential backoff or respect
Retry-Afterheaders.
Pagination
- Many list endpoints return paginated results using a
nextfield in the response. Continue fetching until thenextlink is absent.
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.
dlt ai toolkit data-exploration install dlt ai toolkit dlthub-runtime install
Was this page helpful?
Community Hub
Need more dlt context for Oscar?
Request dlt skills, commands, AGENT.md files, and AI-native context.