Webflow API Limitations

From a practical standpoint, these are some of the biggest limitations I've encountered;

CMS + Rich Text Content

HTML Embeds

There are some known problems with updating Rich Text content specifically around HTML Embeds.

https://discourse.webflow.com/t/cms-api-stripping-html-embeds/118314/12

CMS Item APIs

• Collection ID's and Collection Item ID's are not persistent across backup-restores. That means if you have an external integration that relies on these ID's, they all change if the site is restored from a backup.
• Inability to determine a "first time published" status on CMS items
• Inability to get a basic count of items in a collection
• Inability to find a CMS item by slug
• Inability to get/update/delete a specific CMS item directly by slug as a unique key

Membership APIs

• Inability to change the Access Groups of a User.
  However this is in BETA.

Note: MemberID's appear to persist reliably across backup restorations.

I'm hopeful to see those abilities in 2023, as Webflow is making some big investments in expanding CMS capability.

‍