redPIM Developer Portal — REST API, OpenAPI & MCP Server

Overview

redPIM is the source of truth for product data: catalogs, categories, products, variants, classification (eClass · ETIM · proficlass), media and exports. Everything you can do in the redPIM web app is backed by a REST API under a predictable URL scheme.

REST API

JSON over HTTPS at https://app.redpim.de/api. Action-method routing: /api/{Controller}/{Action}.

OpenAPI 3.1

Machine-readable contract at /openapi.json — import it into Postman, code generators or agents.

MCP server

Streamable-HTTP MCP server exposing redPIM operations as tools for Claude, ChatGPT & other agents.

Sync connector

A fingerprint-based sync contract for shops/ERPs: mappings → inventory → upsert.

Authentication

API calls run in the context of an authenticated redPIM account. Today that is an authenticated session (cookie REDPim.Cookie) established at login. Headless, agent-friendly Bearer-token / OAuth 2.0 access is on the roadmap.

Need programmatic access for an agent or integration? Request an API token for your account at me@redcomponents.de. We will document the token header here as soon as it is generally available.

# All endpoints require an authenticated redPIM session.
# Interim (token) usage will look like:
curl -H "Authorization: Bearer $REDPIM_TOKEN" \
     https://app.redpim.de/api/Catalog/GetStats

REST API endpoints

A representative subset — the full surface is described in the OpenAPI specification.

Method	Path	Description
GET	`/api/Catalog/GetStats`	Aggregate catalog / category / product counts.
POST	`/api/Catalog/AddCatalog`	Create a catalog.
POST	`/api/Catalog/UpdateCatalog`	Update a catalog.
POST	`/api/Catalog/AddProduct`	Create a product.
POST	`/api/Catalog/UpdateProduct`	Update a product.
POST	`/api/Catalog/SetValue`	Set a single field value on an element.
POST	`/api/Export/StartExport`	Queue a BMEcat / target-system export (returns a job reference).

Product-data sync connector

For shop and ERP integrations, redPIM acts as the source of truth and syncs via a fingerprint-based diff. Each sync run is three steps:

Step	Call	Purpose
1	`GET /mappings`	Fetch lookup tables (manufacturer, unit, tax IDs). Cache ~1h.
2	`GET /inventory`	NDJSON stream of `{sku, fingerprint}` for managed master products.
3	`POST /upsert`	Send create/update batches (≤1000). Each batch is transactional.

The diff is computed locally: SKU not in the remote list → create; fingerprint differs → update; fingerprint equal → skip. The fingerprint is computed by redPIM (one per master product) so the hash algorithm lives in exactly one place.

The full connector contract (auth, request/response schemas, image-sync queue, fingerprint algorithm) is available on request — contact me@redcomponents.de.

MCP server

redPIM ships a Model Context Protocol server so agents (Claude, ChatGPT and others) can call redPIM natively as tools, over the Streamable HTTP transport.

Manifest: /.well-known/mcp.json
Endpoint: https://app.redpim.de/mcp rollout
Tools: get_catalog_stats, list_catalogs, search_products, upsert_product, start_export

Example client config (Streamable HTTP):

{
  "mcpServers": {
    "redpim": {
      "type": "http",
      "url": "https://app.redpim.de/mcp"
    }
  }
}

The MCP server is built on the official C# MCP SDK with Streamable HTTP transport. Authentication for the public endpoint (OAuth 2.0) is being rolled out — request early access at me@redcomponents.de.

Resources

Resource	URL
OpenAPI specification	https://redpim.de/openapi.json
MCP manifest	https://redpim.de/.well-known/mcp.json
llms.txt	https://redpim.de/llms.txt
Product home	https://redpim.de/