Inriver PIM is automatable through its REST API

Inriver PIM is automatable today through its REST API for customers and partners. The community overview says the API exposes Portal and Control Center behavior and provides endpoints for reading and updating iPMC data and the business model. It says an API key should be treated as a username and password for the portal, and for Control Center as well when the key is generated on an administrator. The 15 May 2026 MCP article says that REST API key is sent in the X-inRiver-APIKey header. The overview limits callers to ten concurrent requests per environment and IP address, a 230 second timeout, and upsert batches of at most 100 first-level entities, 5,000 linked entities, or 100,000 field values. A community manager reply on the same page says the method list and Swagger are available to customers and partners. Inriver's article says MCP support shipped in September 2025 as a wrapper around that REST API. Query Manager fetches entity data and also needs the MCPUser permission in Control Center. Code Writer is for writing and testing REST scripts and requires no authentication. The article names Claude Desktop, VS Code, and Cursor, and it says the connection machine needs Node.js and npm. It does not print server URLs or a repository. The vendor llms.txt describes the platform as cloud-native multi-tenant SaaS. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 6 because read and write are documented and the public method list is gated. The MCP description scores 5 because the article does not give a URL an agent can call. The API is the best path.

Best path today: api · Overall automatability: 6/10