canonical: https://jentic.com/apis/wufoo.com/wufoo

# Wufoo API

The Wufoo REST API allows you to interact with Wufoo forms, entries, reports, users, webhooks, and more. Wufoo is an online form builder that helps users create forms, collect data, and manage submissions. The API exposes 18 endpoints secured with basic authentication.

## For AI agents

Programmatically list all forms, get a specific form. Covers 18 operations with basic authentication.

## Scope

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

## Capabilities

- List all forms
- Get a specific form
- Submit a new entry
- Query and filter Wufoo API records by parameters
- Monitor Wufoo API operational status and events

## Use cases

### Developer Tools Operations

Use the Wufoo API to perform developer tools operations programmatically. The API provides 18 endpoints covering core functionality including list all forms, get a specific form, get form fields.

Example prompt: Call GET /forms.json to list all forms

### Automated Forms Management

Automate forms operations by combining multiple Wufoo API endpoints. Agents can get a specific form and then get form fields in a single workflow.

Example prompt: Call GET /forms/{identifier}.json to get a specific form, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Wufoo 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 basic tokens manually.

Example prompt: Search Jentic for 'list all forms', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /forms.json | List all forms |
| GET | /forms/{identifier}.json | Get a specific form |
| GET | /forms/{identifier}/fields.json | Get form fields |
| POST | /forms/{identifier}/entries.json | Submit a new entry |
| GET | /forms/{identifier}/entries.json | Get form entries |
| GET | /forms/{identifier}/entries/count.json | Get form entries count |
| GET | /forms/{identifier}/comments.json | Get form comments |
| GET | /forms/{identifier}/comments/count.json | Get form comments count |

## Key resources

- **Forms** — Operations related to Wufoo forms
- **Entries** — Operations for managing form entries/submissions
- **Fields** — Operations for retrieving form and report field structures
- **Comments** — Operations for form entry comments
- **Reports** — Operations related to Wufoo reports

## Why Jentic

- **Setup:** Wiring the Wufoo API by hand means setting up its basic auth, resolving your account subdomain host, and handling forms and entries yourself. Through Jentic you install once, import the Wufoo API from the API Directory, store the credential once, and your agent calls it.
- **Permission scoping:** The Wufoo API puts the form identifier in the URL path (/forms/{identifier}/entries.json), so a rule can pin your agent to one form: it can read that form's fields, entries, and comments. You choose the operations it may call, so submitting new entries is not included unless you add it.
- **Credential handling:** Your Wufoo API credential 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 all forms' or 'get entries for a form', and Jentic returns the matching Wufoo API 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 Wufoo API use?

The Wufoo API uses HTTP Basic authentication with username and password. 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 list all forms with the Wufoo API?

Yes. Use the GET /forms.json endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Wufoo 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 list all forms through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'list all forms'. Jentic returns the matching Wufoo API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Wufoo API have?

The Wufoo API exposes 18 endpoints covering forms, entries, fields operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Wufoo operations and credentials the agent may use. Since the Wufoo API carries the form identifier in the URL path, you can pin the agent to a single form and allow only reads of that form's fields, entries, and comments. Submitting new entries with POST /forms/{identifier}/entries.json stays off unless you explicitly add it to the allowed operations.