canonical: https://jentic.com/apis/webflow.com/webflow-api

# Webflow API

webflow.com/webflow-api version 2.0.0. The API exposes 108 endpoints secured with bearer authentication.

## For AI agents

Programmatically get authorization user info, get authorization info. Covers 108 operations with bearer authentication.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Get Authorization User Info
- Resolve ID Token
- List Sites
- Update Site
- Delete Site

## Use cases

### 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.

Example prompt: 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.

Example prompt: 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.

Example prompt: Search Jentic for 'get authorization user info', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| 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 |

## Key resources

- **App_Subscriptions** — Operations for app_subscriptions
- **Asset_Folders** — Operations for asset_folders
- **Assets** — Operations for assets
- **Collections** — Operations for collections
- **Form_Submissions** — Operations for form_submissions

## Why Jentic

- **Setup:** Wiring the Webflow API by hand means learning its bearer token, choosing among the beta, v2, and CDN hosts, and handling responses yourself. Through Jentic you install once, import the Webflow API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Webflow puts the site id in the URL path (/sites/{site_id}), so a rule can pin your agent to one site and nothing else. You choose the operations it may call, so destructive ones like deleting a site are not included unless you add them.
- **Credential handling:** Your Webflow token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list sites' or 'inspect a token', and Jentic returns the matching Webflow operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### 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 your Jentic One instance 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 through Jentic One, the self-hosted execution layer, 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.

### Can I limit what my agent is allowed to do with the Webflow API?

Yes. Because Jentic One is self-hosted, your own rules decide which Webflow operations and credentials the agent may use. Since Webflow puts the site id in the URL path (/sites/{site_id}), a rule can pin the agent to a single site and block everything else. You also choose the exact operations it may call, so destructive ones like DELETE /sites/{site_id} stay out of reach unless you explicitly add them.