redPIM

redPIM Developer Portal

Integrate with redPIM programmatically — the Cloud PIM for technical distributors. REST API, an OpenAPI 3.1 specification, a product-data sync connector, and a Model Context Protocol (MCP) server so AI agents can call redPIM natively.

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

redPIM has two authentication paths, depending on the surface:

Authorization server: https://app.redpim.de/ · Dynamic Client Registration: POST https://app.redpim.de/connect/register · scopes mcp, api, offline_access. The token is issued after a redPIM user logs in at the authorization endpoint and authorizes the client; it then acts on that user's single company. Obtaining a redPIM account itself is still part of onboarding — me@redcomponents.de.
# Agent calls carry an OAuth 2.1 bearer token (scope: api):
curl -H "Authorization: Bearer $REDPIM_TOKEN" \
     https://app.redpim.de/api/ai/GetStats

REST API endpoints

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

MethodPathDescription
GET/api/Catalog/GetStatsAggregate catalog / category / product counts.
POST/api/Catalog/AddCatalogCreate a catalog.
POST/api/Catalog/UpdateCatalogUpdate a catalog.
POST/api/Catalog/AddProductCreate a product.
POST/api/Catalog/UpdateProductUpdate a product.
POST/api/Catalog/SetValueSet a single field value on an element.
POST/api/Export/StartExportQueue 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:

StepCallPurpose
1GET /mappingsFetch lookup tables (manufacturer, unit, tax IDs). Cache ~1h.
2GET /inventoryNDJSON stream of {sku, fingerprint} for managed master products.
3POST /upsertSend 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.

Example client config (Streamable HTTP):

{
  "mcpServers": {
    "redpim": {
      "type": "http",
      "url": "https://mcp.redpim.de/"
    }
  }
}
Built on the official C# MCP SDK (Streamable HTTP). The endpoint is protected by OAuth 2.1 (authorization_code + PKCE): clients discover the authorization server via protected-resource metadata (server card) and self-register via Dynamic Client Registration — connecting from Claude, ChatGPT and other MCP clients works out of the box.

Resources

ResourceURL
OpenAPI specificationhttps://redpim.de/openapi.json
MCP manifesthttps://redpim.de/.well-known/mcp.json
llms.txthttps://redpim.de/llms.txt
Product homehttps://redpim.de/