webflow-common-errors

name	webflow-common-errors
description	Diagnose and fix Webflow Data API v2 errors — 400, 401, 403, 404, 409, 429, 500. Use when encountering Webflow API errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "webflow error", "fix webflow", "webflow not working", "debug webflow", "webflow 429", "webflow 401".
allowed-tools	Read, Grep, Bash(curl:*), Bash(npx:*)
version	1.5.0
license	MIT
author	Jeremy Longshore <[e-mail]>
tags	["saas","design","no-code","webflow"]
compatibility	Designed for Claude Code

Webflow Common Errors

Overview

Quick reference for the most common Webflow Data API v2 errors, their root causes, and concrete solutions. Covers every HTTP status code the API returns.

Prerequisites

• webflow-api SDK installed
• API token configured
• Access to application logs

HTTP Error Reference

400 Bad Request — Invalid Input

{ "code": "validation_error", "message": "Invalid field data" }

Common causes:

• Missing required field (name and slug are always required for CMS items)
• Wrong field type (sending string for a Number field)
• Invalid slug format (must be lowercase, hyphens only, no spaces)
• Bulk request exceeds 100 items

Fix:

// Check collection schema before creating items
const collection = await webflow.collections.get(collectionId);
const requiredFields = collection.fields?.filter(f => f.isRequired);
console.log("Required fields:", requiredFields?.map(f => `${f.slug} (${f.type})`));

// Validate slug format
function isValidSlug(slug: string): boolean {
  return /^[a-z0-9]+(?:-[a-z0-9]+)*$/.test(slug);
}

---

401 Unauthorized — Invalid Token