API by Zapier vs Webhooks by Zapier: Features, Limitations, and Use Cases

A practical field guide from Automation Ace.

The short answer

Use Webhooks by Zapier to receive data pushed to Zapier and for quick HTTP requests. Use API by Zapier for authenticated, repeatable requests to an API and for polling an API that has no webhooks. The deciding factors are direction (receiving vs calling), how authentication is handled, and whether you need to detect new items on a schedule.

Both are built-in Zapier tools for working with any app that has an HTTP API, even without a dedicated Zapier integration. For the concepts behind them, see API vs webhook: when to use each. For more on the platform, see Zapier automation, webhook automation, and custom API integrations.

Feature comparison

Trigger and action names come from Zapier's app directory and help docs at the time of writing. Check how to see an app's triggers and actions for the current list.

API by Zapier: features and use cases

API by Zapier makes authenticated HTTP requests to any API. Its key idea is the connection: you store the API's credentials once, and every API Request step using that connection includes them automatically. That keeps keys out of individual step fields and makes updates easier when a key rotates.

• API Request (action): set the method, URL, headers, and body; the response is available to later steps.
• New Item from API (Polling) (trigger): Zapier calls an endpoint on a schedule, uses a Response Filter to find the list of items and a Dedupe Key to recognize which ones are new, then runs the Zap once per new item.

Great for: apps with no Zapier integration, endpoints a native integration does not cover (compare with the API Request action inside app integrations), and detecting new records in APIs that do not send webhooks.

Webhooks by Zapier: features and use cases

Webhooks by Zapier is Zapier's general-purpose HTTP tool, strongest at receiving data.

• Catch Hook (trigger): gives you a unique URL; anything that POSTs to it starts the Zap with parsed fields.
• Catch Raw Hook (trigger): accepts GET, PUT, or POST and passes the unparsed body and headers, useful for signature verification or unusual formats.
• Retrieve Poll (trigger): makes a GET request to a URL on a schedule to look for new entries.
• GET, POST, PUT, Custom Request (actions): send HTTP requests with form, JSON, XML, or raw payloads.

Great for: receiving events from apps with webhook support (see Contact Form 7, Wix, and Gravity Forms examples), chaining Zaps, and simple outbound calls such as triggering an Airtable automation.

Limitations to know

• Payload sizes (Webhooks by Zapier): Zapier documents limits of about 10 MB for trigger payloads, 2 MB for Catch Raw Hook, and 5 MB for action payloads, with oversized requests rejected. Confirm current values.
• Rate limits: Zapier applies rate limits to webhook URLs, and the APIs you call have their own. See 429 errors.
• Timeouts: slow endpoints can time out. See HTTP request timeout errors.
• Polling cost and delay (both): polling triggers run on your plan's interval and can use tasks. See polling vs instant triggers.
• Pagination: neither tool pages through large result sets automatically in every case; you may need looping or a Code step.
• Plan availability: these are premium built-in tools on many Zapier plans. Check your plan.

Which should you choose?

1. Need an app to push data into Zapier? Webhooks by Zapier (Catch Hook).
2. Calling the same authenticated API repeatedly? API by Zapier.
3. Need to detect new items in an API with no webhooks? API by Zapier's polling trigger (or Retrieve Poll for simple unauthenticated GETs).
4. One quick call to a public or simple endpoint? Webhooks by Zapier action.
5. Complex logic, loops, or signing? Add a Code step alongside either.

Many Zaps use both: Catch Hook to start, API Request to fetch details and update systems. See passing data between API requests and webhooks and API authentication for automation.

Frequently asked questions

What is the difference between API by Zapier and Webhooks by Zapier?

Webhooks by Zapier is strongest at receiving data through Catch Hook URLs and also sends simple HTTP requests. API by Zapier makes authenticated API requests using a stored connection and can poll an API for new items.

Can API by Zapier receive webhooks?

No. To receive inbound webhooks in Zapier, use the Webhooks by Zapier Catch Hook or Catch Raw Hook trigger.

What triggers does Webhooks by Zapier have?

Catch Hook, Catch Raw Hook, and Retrieve Poll. Catch Hook parses incoming data, Catch Raw Hook passes the raw body and headers, and Retrieve Poll checks a URL on a schedule.

How does API by Zapier detect new items?

Its New Item from API polling trigger calls an endpoint on a schedule, uses a Response Filter to locate the list of items, and uses a Dedupe Key to identify which items are new.

What are the payload limits for Webhooks by Zapier?

Zapier documents roughly 10 MB for trigger payloads, 2 MB for Catch Raw Hook, and 5 MB for action payloads. Check Zapier's help center for current limits.