Troubleshooting and Fixing Webflow API Issues for Improved Data Organization
In this meeting, the State Changers are focused on debugging an API issue with the Webflow CMS. The issue arises when trying to make a request with Webflow. The first issue found was apparent in the authorization header, where an "access_token" was being added unnecessarily. This led to duplication in headers, causing the API request to fail. A correction was made by inserting the Webflow API Key directly into the API call authorization header.
However, this solution did not entirely solve the problem. Another issue was found, which related to the case sensitivity of the fields in the parameters. It was highlighted that 'Name' and 'Slug' fields were being passed with an uppercase first letter which the payload wasn't recognizing, and the issue needed changing them to lowercase in the payload for the machine to correctly read them.
The facilitator shared a link to developers.webflow.com in the chat to demonstrate how the field names should appear in the payload, making sure they are lowercase. A team member, David, agreed to continue debugging the problem so the meeting could progress along and not keep others waiting. The main tools used in this meeting for debugging were Zano and the Webflow CMS.