Webflow API
Browse all Webflow APIs✓ Official Vendor SpecDeveloper ToolsSource Controlbearer108 EndpointsREST
For Agents
Programmatically get authorization user info, get authorization info. Covers 108 operations with bearer authentication.
Use for: I need to authorization user info, I want to authorization info, Search for resolve id token, Find all sites
Not supported: Does not handle payments, communications, or crm — use for developer tools only.
webflow.com/webflow-api version 2.0.0. The API exposes 108 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the Webflow API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Webflow API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Webflow API.
Get Authorization User Info
Resolve ID Token
List Sites
Update Site
Delete Site
Use Cases
Patterns agents use Webflow API for, with concrete tasks.
★ Developer Tools Operations
Use the Webflow API to perform developer tools operations programmatically. The API provides 108 endpoints covering core functionality including get authorization user info, get authorization info, resolve id token.
Call GET /token/authorized_by to get authorization user info
Automated App_Subscriptions Management
Automate app_subscriptions operations by combining multiple Webflow API endpoints. Agents can get authorization info and then resolve id token in a single workflow.
Call GET /token/introspect to get authorization info, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Webflow API endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle bearer tokens manually.
Search Jentic for 'get authorization user info', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
108 endpoints — webflow.
METHOD
PATH
DESCRIPTION
GET
/token/authorized_by
Get Authorization User Info
GET
/token/introspect
Get Authorization Info
POST
/token/resolve
Resolve ID Token
GET
/sites
List Sites
GET
/sites/{site_id}
Get Site
PATCH
/sites/{site_id}
Update Site
DELETE
/sites/{site_id}
Delete Site
GET
/sites/{site_id}/custom_domains
Get Custom Domains
GET
/token/authorized_by
Get Authorization User Info
GET
/token/introspect
Get Authorization Info
POST
/token/resolve
Resolve ID Token
GET
/sites
List Sites
GET
/sites/{site_id}
Get Site
PATCH
/sites/{site_id}
Update Site
DELETE
/sites/{site_id}
Delete Site
GET
/sites/{site_id}/custom_domains
Get Custom Domains
Why Jentic?
Three things that make agents converge on Jentic-routed access.
Credential isolation
Webflow API bearer credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.
Intent-based discovery
Agents search by intent (e.g., 'get authorization user info') and Jentic returns the matching Webflow API operation with its input schema, so the agent can call the right endpoint without browsing docs.
Time to first call
Direct Webflow API integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Github
Alternative developer tools API
Choose Github when you need a different approach to developer tools operations
FAQs
Specific to using Webflow API through Jentic.
What authentication does the Webflow API use?
The Webflow API uses a Bearer token in the Authorization header. Through Jentic, these credentials are stored encrypted in the MAXsystem vault and injected at execution time, so raw secrets never enter the agent context.
Can I get authorization user info with the Webflow API?
Yes. Use the GET /token/authorized_by endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Webflow API?
Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer.
How do I get authorization user info through Jentic?
Install the Jentic SDK with pip install jentic, authenticate at https://app.jentic.com/sign-up, then search for 'get authorization user info'. Jentic returns the matching Webflow API operation with its input schema. Load the schema and execute the call — credentials are injected automatically.
How many endpoints does the Webflow API have?
The Webflow API exposes 108 endpoints covering app_subscriptions, asset_folders, assets operations.
GET STARTED