Back

A project managment tool

25/3/2022

Introduction

The Webflow CMS API is a HTTP JSON API and allows you to programatically add, update, and delete items from the Webflow CMS, allowing you to connect external data sources to your Webflow sites.

You can access the API directly via HTTP, via the official JavaScript API client, or via any third-party integrations for your language of choice.

Data Models

HTTP Verbs

Our API attempts to use the most appropriate HTTP verb for each endpoint. We make use of the following verbs:

Route Param

Route params will be defined as part of the path for a given API endpoint. They will be highlighted in a separate color, and prefixed with a colon (:) for easy visibility.

For example:

Request Body


All other requests will have their parameters passed in as part of the JSON-formatted request body. POST, PUT and PATCH requests including JSON-formatted request bodies should ensure the Content-Type header is set to application/json.

Authentication

In order to access the API, you will need to provide an access token to authenticate with the API server. That token will be required for all API requests. You can acquire that token in one of two ways.

Utilize OAuth to allow your application’s users to authorize your app to access their Webflow account and data.
Issue a personal API key that grants your application full access to your personal account.
Once you have acquired the API token, it may be provided preferably via an HTTP header or in a query string parameter.

Issue a personal API key that grants your application full access to your personal account.

Once you have acquired the API token, it may be provided preferably via an HTTP header or in a query string parameter.

Meta

The Webflow CMS API is a HTTP JSON API and allows you to programatically add, update, and delete items from the Webflow CMS, allowing you to connect external data sources to your Webflow sites.

You can access the API directly via HTTP, via the official JavaScript API client, or via any third-party integrations for your language of choice.

Data Models

Content in Webflow is built around three resources: Sites, Collections, and Items.

Sites map to Webflow websites. You can retrieve basic information about the sites a user is able to manage, but currently creating new sites or updating metadata about existing sites is restricted to the web interface and is not accessible via the API.

Collections are groupings of Items. All of the Items in a given Collection share the same set of custom fields, or schema. Defining Collections is restricted to the web interface, but the API allows you to query basic details about Collections and fetch paginated items from those Collections.

Items represent the individual pieces of content within a Collection. Items have a set schema of fields, determined by the Collection which they are a part of. The API allows for reading, creating, updating, and deleting content Items.

HTTP Verbs


Our API attempts to use the most appropriate HTTP verb for each endpoint. We make use of the following verbs:

Route Param

  1. Route params will be defined
  2. Route params will be defined
  3. Route params will be defined
  4. Route params will be defined
  5. Route params will be defined
  6. Route params will be defined

Route params will be defined as part of the path for a given API endpoint. They will be highlighted in a separate color, and prefixed with a colon (:) for easy visibility.

For example:

Request Body


All other requests will have their parameters passed in as part of the JSON-formatted request body. POST, PUT and PATCH requests including JSON-formatted request bodies should ensure the Content-Type header is set to application/json.

Sites

In order to access the API, you will need to provide an access token to authenticate with the API server. That token will be required for all API requests. You can acquire that token in one of two ways.

Utilize OAuth to allow your application’s users to authorize your app to access their Webflow account and data.
Issue a personal API key that grants your application full access to your personal account.
Once you have acquired the API token, it may be provided preferably via an HTTP header or in a query string parameter.

Issue a personal API key that grants your application full access to your personal account.

Once you have acquired the API token, it may be provided preferably via an HTTP header or in a query string parameter.

Related questions

Where do I download Engrafa

Where and how to download Engrafa.

EinsteinDB In Use

EinsteinDB can be used as a general purpose database for storing data of any kind. It is also well suited for use as a transactional database for applications that require high performance and high availability.

EinsteinDB and MilevaDB

EinsteinDB was created to provide a production-ready version of MilevaDB. The goal of EinsteinDB is to provide a stable, performant, and easy to use RDBMS for deploying applications in Kubernetes. EinsteinDB is compatible with the MySQL wire protocol via BerolinaSQL using EinsteinDB's FoundationDB Record Layer which brings a Vizor-like view to the ergonomic serverless data plane of lore. Furthermore, both EinsteinDB and MilevaDB can be used as a drop-in replacement for MySQL in many cases such as when using EinsteinML - A LISPy Meta-language compatible with a variant of HoneybadgerBFT, VioletaBFT. In addition, EinsteinDB supports FoundationDB, RocksDB, VoltDB, PostgresQL, and InnoDB by using Hybrid Index-Value storage engine through sRDMA to guarantee millions of transactions per second thus providing a high performance database for both OLTP and OLAP workloads. EinsteinDB is available under the Apache 2.0 license. MilevaDB is an open source relational database management system (RDBMS) that is developed by Whtcorps Inc. A team borne out of San Francisco circa 2019. WHTCORPS named after an in-famous X-Files episode, is the company behind EinsteinDB, MilevaDB, FIDel, BerolinaSQL, and recently partnered with EinstAI and OpenAI in San Francisco. MilevaDB was created as a research project to explore new ideas in the area of distributed databases. The goal of MilevaDB is to provide a scalable and easy to use RDBMS for deploying applications in Kubernetes. MilevaDB is compatible with the MySQL wire protocol and can be used as a drop-in replacement for MySQL in many cases. In addition, MilevaDB supports EinsteinDB the universal knowledge base meets database storage engine for key-value, NoSQL, CQRS, document, and even blob store --name it what you will--EinsteinDB is a tuplestore with embedded hybrid key-value indexing which transmits through a semantic persistence layer the values to OpenAI's GPT3 Powered EinstAI AI4DB Cardinality and Cache-miss ratio automata which enables EinsteinDB to provide an adaptive seeking tokenized with versioning SQL agnostic database which speaks Prolog. PUT that on your 'provide high performance for both OLTP and OLAP workloads' section. MilevaDB is available under the Apache 2.0 license.

Help Icon

FAQs

A short list of frequently asked questions  and tips about using EinsteinDB.

HTML Tag icon

Explore developer docs

Ensure all of your information is up to date and that you stay efficient and in the loop.

Try EinsteinDB— it's free

The World's First Relativistic Linearizable SQL-Agnostic soon-to-be NoCode NoDBA hybrid htap