Update/create several attributes in Akeneo PIM
A documented Akeneo PIM operation that changes something in your account. Describe the outcome you want in plain words — HumDay writes the program, proves it, and runs it.
What this operation does
Update/create several attributes
- PATCHChanges data · Attribute
demo.akeneo.com/api/rest/v1/attributes
How HumDay uses it
- You describe the outcome. Not this operation by name — what you want to happen. HumDay works out which operations it needs.
- The contract names it. Before anything is built, you see exactly which Akeneo PIM operations the program may use, and this is one of them.
- You approve access. Because this one changes data, it cannot run until you have explicitly granted it.
Other Akeneo PIM operations
- Create a new channelPOST · changes data
- Create a new product media filePOST · changes data
- Create a new media file for an assetPOST · changes data
- Create a new media file for a reference entity or a recordPOST · changes data
- Update/create several channelsPATCH · changes data
- Update/create a channelPATCH · changes data
- Create a new PAM assetPOST · changes data
- Create a new catalogPOST · changes data
Questions
- Can HumDay update/create several attributes in Akeneo PIM?
- Yes. This operation is published in Akeneo PIM's own API description, so HumDay can use it without a hand-built connector — once you have approved it for your automation.
- Will this change my Akeneo PIM data?
- Yes — this is a PATCH operation, so it changes something in Akeneo PIM. HumDay holds anything that writes behind an approval you grant explicitly, and the contract you approve says what it may touch.
- Do I need to write code?
- No. You describe the outcome you want in plain words. HumDay agrees a contract with you, writes the program, and shows you a proof run before anything touches your Akeneo PIM account.
Where this came from
Read from a published API description for Akeneo PIM at raw.githubusercontent.com/akeneo/pim-api-docs/master/content/swagger/akeneo-web-api.json. The description above is the provider’s own wording, not ours. Last published 2023-03-06.