[API] Product Features (Keys & Notes) to be created and attached to a product via the Products API
I am building an integration of Creem with Strapi and currently, I see the following when trying to add features like how it’s done in the Creem dashboard — there is no way to create them via the Products API or a standalone API and then attach them to a product. This forces a dashboard-first workflow and breaks fully API-driven or code-first setups.
It would be great to either:
Extend the Products API to support creating features directly, or
Provide a standalone API endpoint for creating features that can then be associated with a product
This would help me make the Creem plugin for Strapi be truly Strapi-first for the developers.

Log in to comment and vote
Comments1
jayrabe
Aug 12
Seconding this from a catalog-automation angle. We built our own sync tool against the products API and these are the fields it can't touch:
License-key settings are dashboard-only — activation limit, key-enable, expiration — so a keys-enabled product can never be fully managed from a script.
Trial configuration is also dashboard-only AND doesn't appear in the API product object, so a synced or exported product can't even tell that it has a trial.
A price change via the API mints a new default price object rather than editing in place, which is surprising for automation (one doc line would set expectations).
The practical effect is that any merchant automating their catalog has to leave the keyed products half-manual, which is exactly where a proven config picks up a typo.