Emigo Data Source Python API Docs | dltHub
Build a Emigo Data Source-to-database pipeline in Python using dlt with AI harness support for Claude Code, Cursor, and Codex.
Last updated:
Emigo is a data management and integration system by Sagra Technology for synchronizing business data across enterprise platforms. The REST API base URL is The official Emigo API documentation does not publicly specify a REST API base URL. and Authentication is handled via OAuth 2.0..
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 Emigo Data Source data in under 10 minutes.
What data can I load from Emigo Data Source?
Here are some of the endpoints you can load from Emigo Data Source:
| Resource | Endpoint | Method | Data selector | Description |
|---|---|---|---|---|
| feeds | GetFeeds | GET | FeedList | Retrieve list of available feeds |
| odata_items | GetODataItems | GET | FeedList | Retrieve OData items for a specific endpoint and feed |
| operational_units | GetOperationalUnitItem | GET | Retrieve a specific operational unit by ID | |
| items | GetItems | GET | Retrieve items by table type (deprecated) | |
| messages | SendMessage | POST | Send a message to an operational unit |
How do I authenticate with the Emigo Data Source API?
The Emigo connector uses OAuth 2.0 authentication; users sign in with their instance credentials.
1. Get your credentials
Emigo uses OAuth 2.0 authentication for its integrations. To obtain credentials, log in to your Emigo instance through the standard user interface or the designated administrative portal provided by Sagra Technology to authorize your application or integration. There is no traditional static API key/secret dashboard for direct REST API access in the standard connector documentation; rather, it uses OAuth 2.0 flow to link your account.
2. Add them to .dlt/secrets.toml
[sources.emigo_data_source_source] client_id = "your_client_id_here" client_secret = "your_client_secret_here" refresh_token = "your_refresh_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 harness:
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:
dlthub 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 Emigo Data Source 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 emigo_data_source_pipeline.py
If everything is configured correctly, you'll see output like this:
Pipeline emigo_data_source_pipeline load step completed in 0.26 seconds 1 load package(s) were loaded to destination duckdb and into dataset emigo_data_source_data The duckdb destination used duckdb:/emigo_data_source.duckdb location to store data Load package 1749667187.541553 is LOADED and contains no failed jobs
Inspect your pipeline and data:
dlt pipeline emigo_data_source_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 connections and datasets (Note: As Emigo is primarily accessed via a managed Power Platform connector, direct REST API endpoint documentation is not publicly exposed; these are the standard placeholders for data pipeline configurations using managed connectors). from the Emigo Data Source 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 emigo_data_source_source(api_key=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "The official Emigo API documentation does not publicly specify a REST API base URL.", "auth": {"type": "api_key", "api_key": api_key}, }, "resources": [ {"name": "feeds", "endpoint": {"path": "GetFeeds", "data_selector": "FeedList"}}, {"name": "odata_items", "endpoint": {"path": "GetODataItems", "data_selector": "FeedList"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="emigo_data_source_pipeline", destination="duckdb", dataset_name="emigo_data_source_data", ) load_info = pipeline.run(emigo_data_source_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("emigo_data_source_pipeline").dataset() sessions_df = data.feeds.df() print(sessions_df.head())
SQL (DuckDB example):
SELECT * FROM emigo_data_source_data.feeds LIMIT 10;
In a marimo or Jupyter notebook:
import dlt data = dlt.pipeline("emigo_data_source_pipeline").dataset() data.feeds.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 Emigo Data Source 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.
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.
dlthub ai toolkit data-exploration install dlthub ai toolkit dlthub-platform install
Was this page helpful?
Community Hub
Need more dlt context for Emigo Data Source?
Request dlt skills, commands, AGENT.md files, and AI-native context.