Euromaster Party API Python API Docs | dltHub

Build a Euromaster Party API-to-database pipeline in Python using dlt with AI Workbench support for Claude Code, Cursor, and Codex.

Last updated:

The Euromaster Party API offers endpoints for managing retail customer data and high-value functionalities. It uses OAuth 2.0 for authorization. The VCS API provides vehicle inspection data for fleets. The REST API base URL is https://api.euromaster.com/party-erm/v1 and Requests require a client-id header plus HTTP Basic authentication (client credentials) to obtain access/identify the caller..

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 Euromaster Party API data in under 10 minutes.


What data can I load from Euromaster Party API?

Here are some of the endpoints you can load from Euromaster Party API:

| Resource | Endpoint | Method | Data selector | Description | | --- | ---: | ---: | ---: | | | parties_extended | /party-erm/v1/parties/extended | GET | (response contains pagination object; top-level records unclear — use full response) | Get parties extended data (paginated) | | parties | /party-erm/v1/parties | GET | (top-level array? docs show single object examples; use parties for list endpoints) | Get parties | | parties_quick_search | /party-erm/v1/parties/quick-search | GET | (top-level array) | Quick search parties (returns top-level array of parties) | | party_by_code | /party-erm/v1/parties/{partyCode} | GET | (single object) | Get a party by code | | party_extended_by_code | /party-erm/v1/parties/{partyCode}/extended | GET | (single object) | Get a party with extended info | | party_me | /party-erm/v1/parties/me | GET | (single object) | Get authenticated user's party | | party_me_sites | /party-erm/v1/parties/me/sites | GET | sites | Get sites for current user (paginated) | | party_me_users | /party-erm/v1/parties/me/users | GET | users | Get users associated with current user's party (paginated; response contains "pagination" and "users") | | party_me_contacts | /party-erm/v1/parties/me/contacts | GET | contacts | Get contacts for current user (paginated; response contains "pagination" and "contacts") | | sites | /party-erm/v1/sites | GET | (paginated) | Get sites data | | site_by_code | /party-erm/v1/sites/{siteCode} | GET | (single object) | Get a site | | offers | /party-erm/v1/offers | GET | (paginated) | Get offers data | | offer_by_code | /party-erm/v1/offers/{offerCode} | GET | (single object) | Get an offer | | users_me_user | /party-erm/v1/parties/me/users/{userCode} | GET | (single object) | Get a specific user belonging to authenticated user's party |


How do I authenticate with the Euromaster Party API API?

The API requires identification with a provided client id header and uses Basic auth (client credentials) for authorization. Include the client id header in each request and perform the Basic auth flow to authenticate (Authorization: Basic base64(clientId:clientSecret) where required by the gateway). Use the appropriate APIGEE environment URL (prod/preprod/indus) as needed.

1. Get your credentials

  1. Register or request access on Euromaster Developers Portal (https://developer.euromaster.com/portal/) and request Party API access.
  2. Once granted, obtain the assigned client id and client secret from the portal or your Euromaster API contact.
  3. Use the provided client id in the required request header and use Basic auth (client id/client secret or gateway-specified flow) as described in the Party API technical documentation to authenticate.

2. Add them to .dlt/secrets.toml

[sources.euromaster_party_api_source] client_id = "your_client_id_here" client_secret = "your_client_secret_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 Euromaster Party API 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 euromaster_party_api_pipeline.py

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

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

Inspect your pipeline and data:

dlt pipeline euromaster_party_api_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 parties and parties/extended from the Euromaster Party API 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 euromaster_party_api_source(client_secret=dlt.secrets.value): config: RESTAPIConfig = { "client": { "base_url": "https://api.euromaster.com/party-erm/v1", "auth": { "type": "http_basic", "client_secret": client_secret, }, }, "resources": [ {"name": "parties", "endpoint": {"path": "party-erm/v1/parties"}}, {"name": "party_me_users", "endpoint": {"path": "party-erm/v1/parties/me/users", "data_selector": "users"}} ], } yield from rest_api_resources(config) def get_data() -> None: pipeline = dlt.pipeline( pipeline_name="euromaster_party_api_pipeline", destination="duckdb", dataset_name="euromaster_party_api_data", ) load_info = pipeline.run(euromaster_party_api_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("euromaster_party_api_pipeline").dataset() sessions_df = data.parties.df() print(sessions_df.head())

SQL (DuckDB example):

SELECT * FROM euromaster_party_api_data.parties LIMIT 10;

In a marimo or Jupyter notebook:

import dlt data = dlt.pipeline("euromaster_party_api_pipeline").dataset() data.parties.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 Euromaster Party API 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 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 Euromaster Party API?

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