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

# EZ File Drop API

Jentic publishes the only available OpenAPI specification for EZ File Drop API, keeping it validated and agent-ready. EZ File Drop is a file-collection service whose Zapier-flavoured integration API lets external systems retrieve form submissions and subscribe to webhooks when new submissions arrive. The four endpoints cover authentication validation, listing submissions, and registering a webhook target, with an X-ZAP-KEY API key authenticating every request.

## For AI agents

Retrieve EZ File Drop form submissions and subscribe to webhooks for new file drops via four Zapier-style endpoints under www.ezfiledrop.com.

## Scope

Does not handle file storage, e-signature, or content moderation - use for retrieving EZ File Drop form submissions and webhook subscriptions only.

## Capabilities

- Validate the configured X-ZAP-KEY API key via /third-party/zapier/auth-test
- Retrieve the list of submitted forms and uploaded files through /third-party/zapier/submissions
- Register a webhook callback for new submissions via /third-party/zapier/subscribe
- Cancel a webhook subscription when integration logic no longer needs notifications
- Drive bulk pulls of submissions on a schedule when webhooks are not desired

## Use cases

### Pull-Based Submission Sync

Periodically fetch new submissions from EZ File Drop using the /third-party/zapier/submissions endpoint and ingest them into a downstream system such as a CRM or document store. Use the X-ZAP-KEY API key in the request header and treat newer submissions as the authoritative payload. Suitable for environments where outbound webhooks cannot be received.

Example prompt: Schedule a job that calls GET /third-party/zapier/submissions every five minutes and forwards new entries to the destination system.

### Webhook-Driven File Processing

Subscribe to EZ File Drop submissions via /third-party/zapier/subscribe so that downstream systems are notified the moment a new form is submitted. The webhook callback receives the submission payload, allowing immediate file processing, virus scanning, or automatic forwarding into a document workflow without polling.

Example prompt: POST a target URL to /third-party/zapier/subscribe with the X-ZAP-KEY header to register a webhook for new submissions.

### Connectivity Healthcheck

Confirm that the configured API key is valid before scheduling integration work by calling /third-party/zapier/auth-test. Useful for build pipelines or CI checks that need a green-light signal before granting downstream services access to real submission data, and as a smoke test after rotating the X-ZAP-KEY value.

Example prompt: Call GET /third-party/zapier/auth-test with the X-ZAP-KEY header and assert a 2xx response before proceeding with submission sync.

### Agent-Driven File Drop Triage via Jentic

An AI agent monitoring inbound files can use Jentic to subscribe to EZ File Drop submissions and pull payloads when notified, without embedding the Zapier integration logic. The X-ZAP-KEY value lives in your Jentic One instance, so the agent can register webhooks and pull new submissions while the credential never enters its prompt context.

Example prompt: Through Jentic, search 'subscribe to EZ File Drop submissions', load /third-party/zapier/subscribe, and execute it with the agent's webhook URL.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /third-party/zapier/auth-test | Validate the configured API key |
| GET | /third-party/zapier/submissions | List form submissions |
| POST | /third-party/zapier/subscribe | Register a webhook for new submissions |
| DELETE | /third-party/zapier/subscribe | Cancel a webhook subscription |

## Key resources

- **Auth test** — Validate the X-ZAP-KEY API key
- **Submissions** — Retrieve form submissions and file metadata
- **Subscribe** — Register webhook callbacks for new submissions

## Why Jentic

- **Setup:** Wiring the EZ File Drop API by hand means registering its X-ZAP-KEY scheme, targeting the www.ezfiledrop.com host, and managing the Zapier-style submission and webhook routes yourself. Through Jentic you install once, import the EZ File Drop API from the API Directory, store the API key once, and your agent calls it.
- **Permission scoping:** EZ File Drop carries webhook targets in the request body rather than a resource id in the path, so you limit the agent to the operations it needs, such as pulling submissions or subscribing to a webhook. You choose those operations, so the subscription-delete call is not included unless you add it.
- **Credential handling:** Your EZ File Drop X-ZAP-KEY is stored once, encrypted, by your own Jentic One instance and injected as a request header at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'subscribe to EZ File Drop submissions' or 'pull recent form submissions', and Jentic returns the matching /third-party/zapier operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **EziDox API** — Document management and e-signature workflows - useful when collected files need to be routed for signature.
- **ezeep Blue Printing API** — Cloud printing - pair with EZ File Drop when each submitted file should be printed automatically.

## FAQ

### Why is there no official OpenAPI spec for EZ File Drop API?

EZ File Drop does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call EZ File Drop API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the EZ File Drop API use?

The spec declares an apiKey scheme called apiKeyAuth that requires the X-ZAP-KEY header on every request. Generate the key from your EZ File Drop account and store it in your Jentic One instance so it is never written into agent prompts.

### Can I subscribe to new submissions with the EZ File Drop API?

Yes. POST your callback URL to /third-party/zapier/subscribe with the X-ZAP-KEY header to start receiving webhook notifications whenever a new submission lands.

### How do I confirm the API key is valid?

Call GET /third-party/zapier/auth-test with the X-ZAP-KEY header; a 2xx response confirms the key is active and authorised for the four Zapier-style endpoints.

### How do I subscribe to submissions through Jentic?

Run pip install jentic, search 'subscribe to EZ File Drop submissions', load /third-party/zapier/subscribe, then execute it with your webhook URL; Jentic injects the X-ZAP-KEY from the vault.

### What are the rate limits for the EZ File Drop API?

The spec does not declare explicit rate limits, so honour any 429 responses with backoff and prefer the webhook subscribe endpoint over high-frequency polling of /third-party/zapier/submissions.

### Can I limit what my agent is allowed to do with the EZ File Drop API?

Yes. Because Jentic One is self-hosted, your own rules decide which of the four EZ File Drop operations the agent may call, so you can allow it to list submissions at GET /third-party/zapier/submissions and register a webhook via POST /third-party/zapier/subscribe while withholding the DELETE that cancels a subscription. You choose the operations the agent is permitted to run, and any you leave out are simply unavailable to it. The X-ZAP-KEY credential stays in your own instance and is injected as a request header at execution time, never entering the agent's prompt or context.