How to integrate a REST API with a dashboard UI on Webflow Cloud without exposing your API token

Integrating a REST API dashboard with Webflow Cloud requires a supported Next.js 15+ application using npm, a Webflow site plan appropriate for the intended mount path, local Node.js tooling, and REST API credentials kept in server-side environment secrets. The recommended architecture uses a Next.js Route Handler to call the upstream API, validate and reduce its response to only the dashboard fields, while a client-rendered page fetches that handler using a manually configured base-path prefix so requests work when the app is mounted below the site root. Deployment depends on committing the npm lockfile, configuring the deployed token and matching mount-path variable, and avoiding the unsupported Next.js `runtime = 'edge'` directive despite Webflow Cloud running applications on Cloudflare Workers. Common failures include missing base paths, incorrectly configured secrets that cause upstream authorization errors, and middleware incompatibilities after upgrading Next.js, particularly the shift from supported `middleware.ts` in Next.js 15 to unsupported Node-based `proxy.ts` behavior in later versions. The approach can be extended to CRM data, filtered API requests, and Webflow CMS content, but public routes using token-funded APIs should be protected with authentication, rate limits, and vendor spend controls.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.