Akeneo PIM is automatable through its API

Akeneo PIM is automatable today through its REST API. The connector authentication guide says a connection supplies a client ID, a secret, a username, and a password. The client posts those to /api/oauth/v1/token with grant_type password and an Authorization Basic header of the base64 client ID and secret. The response is JSON with a bearer access token that lasts 3600 seconds and a refresh token. The guide says the refresh token expiration is 1209600 seconds, which is 14 days. Later calls send Authorization Bearer. The REST reference lists create, read, update, and delete for products, product models, families, attributes, assets, reference entities, and related resources. Locales and currencies are listed as reads. The Event Platform documents HTTPS subscriptions. A subscription for com.akeneo.pim.v1.product.updated posts the event to a destination URL after the caller sends the PIM token and client ID. Akeneo also documents a hosted MCP server at https://server.mcp.akeneo.cloud/mcp. The getting-started page says availability may vary by package, that the caller supplies a PIM SaaS URL, and that the same connection credentials are sent as headers. The overview table marks products, families, attributes, categories, assets, reference entities, and workflows as readable, and most of those as writable. It marks product media files, jobs, and catalogs as unsupported. Zapier, Make, Power Automate, and n8n were not opened. Computer-use viability is unassessed. The API scores 8. The MCP server scores 7. The API is the best path because the reference covers media files, jobs, and catalogs that the MCP table leaves unsupported, and because the getting-started page says MCP availability depends on the package.

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