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

# ZenRows API

Web scraping API with anti-bot bypass, residential proxies, and headless browser support. Handles CAPTCHAs, JavaScript rendering, and advanced scraping scenarios. The API exposes 2 endpoints secured with apiKey authentication.

## For AI agents

Programmatically scrape url with post data, scrape url. Covers 2 operations with apiKey authentication.

## Scope

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

## Capabilities

- Scrape URL with POST data
- Manage crm data programmatically
- Integrate ZenRows API into automated workflows
- Query and filter ZenRows API records by parameters
- Monitor ZenRows API operational status and events

## Use cases

### CRM Operations

Use the ZenRows API to perform crm operations programmatically. The API provides 2 endpoints covering core functionality including scrape url with post data, scrape url.

Example prompt: Call POST / to scrape url with post data

### Data Retrieval and Monitoring

Query ZenRows API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary ZenRows API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'scrape url with post data', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | / | Scrape URL with POST data |
| GET | / | Scrape URL |

## Key resources

- **default** — Operations related to default

## Why Jentic

- **Setup:** Wiring ZenRows by hand means passing its apikey in the query string on every request, choosing the GET or POST form of the single scraping endpoint on api.zenrows.com/v1, and coding the request handling yourself. Through Jentic you install once, import ZenRows from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** ZenRows carries the target URL in the request rather than as a resource id in the URL path, so limit the agent to the operations it needs, such as the GET or POST scrape. You choose which of the two forms the agent may call.
- **Credential handling:** Your ZenRows key 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 'scrape a URL' or 'scrape with POST data', and Jentic returns the matching ZenRows operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the ZenRows API use?

The ZenRows API uses an API key passed in the `apikey` query. 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 scrape url with post data with the ZenRows API?

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

### What are the rate limits for the ZenRows 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 scrape url with post data through Jentic?

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

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

The ZenRows API exposes 2 endpoints covering default operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which ZenRows operations and credentials the agent may use. The API has just two forms of the scrape endpoint, the GET scrape and the POST scrape that carries request data, so you can allow only the one the agent needs and withhold the other. Since ZenRows passes the target URL inside the request rather than as an id in the path, you control access at the operation level and your stored key is injected only when a permitted call runs.