pim-api-docs
pim-api-docs copied to clipboard
akeneo
Akeneo Web API documentation (contributions are welcomed!)
…e values ## Comparison between NEW and OLD(Current) ## Create category:  ## Update category:  ```sh curl --request PATCH \ --url {URL}/api/rest/v1/categories/master \...
https://akeneo.atlassian.net/browse/PROGX-17 https://akeneo.atlassian.net/browse/AST-1094 Merge only after the feature is deployed https://github.com/akeneo/pim-enterprise-dev/pull/22681 PR env: https://pr-890.api-dev.akeneo.com/
Hi, I recently stumbled upon those small errors, some elements are incorrectly documented as `_items` when the API returns `items`. Thanks!
Update the web API documentation to include the new share link and full path media link properties: - [List assets for an Asset Family](https://api.akeneo.com/api-reference.html#get_assets) - [Get an asset](https://api.akeneo.com/api-reference.html#get_assets__code_) 
The form data looks ok to me and seems to comply with the specs of the media-files api, but I'm getting an error response. invokehttp.response.body {"code":422,"message":"You should at least give...
This is a dump of a Post to send the media file . I am looking at your Curl example for hours now and i do not see the difference...
The family variant creation resource is grouped incorrectly on api docs website due to mismatched tag name in open api spec yaml. Please see the line highlighted on the link...
