Obtain an admin access token by POSTing credentials to `/rest/V1/integration/admin/token`; the response is a quoted token string.
Include the token in all subsequent requests via the `Authorization: Bearer <token>` header.
Create a product by POSTing a product payload to `/rest/V1/products`; required fields include `sku`, `name`, `price`, `status`, `visibility`, `type_id`, and `attribute_set_id`.
Retrieve a product by issuing a GET to `/rest/V1/products/{sku}`, URL-encoding the SKU if it contains special characters.
Update a product by issuing a PUT to `/rest/V1/products/{sku}` with only the changed fields in the request body.
Delete a product by issuing a DELETE to `/rest/V1/products/{sku}`; a successful deletion returns a boolean `true`.
Known gotchas
Admin tokens expire based on the configured token lifetime in Magento admin settings (default 4 hours) — implement token refresh or re-authentication logic for long-running processes.
The `attribute_set_id` must correspond to a valid attribute set in the store; using an invalid or mismatched set causes a 400 error with a generic message that may not clearly indicate the root cause.
For multi-store setups, prefix the endpoint with the store code (e.g., `/rest/en_US/V1/products`) to operate in a specific store view context; using `/rest/all/` propagates changes to all store views.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp