canonical: https://jentic.com/apis/import.io/import-io-rss

# import.io RSS API

The import.io RSS API exposes a feed of crawl runs performed on an extractor. Its single endpoint, GET `/extractor/{extractorId}/runs`, returns an RSS-style feed describing recent runs so consumers can watch run history without polling the run or data APIs. Authentication is via an apikey query parameter. The API complements the data, extraction, run, and schedule surfaces in the import.io platform.

## For AI agents

Read a feed of recent crawl runs for a specific import.io extractor. Useful for monitoring run history without active polling.

## Scope

Does not start crawls, fetch result rows, or schedule extractors - use for monitoring extractor run history only.

## Capabilities

- Subscribe to a feed of recent crawl runs for an extractor
- Surface run history into monitoring dashboards
- Detect new crawl runs without polling the run or data APIs
- Power agent flows that need to react to a new run completing

## Use cases

### Run History Monitoring

Operations teams can plug the RSS feed into monitoring or notification tools to see when crawl runs complete or fail. The feed avoids polling-based load on the run and data APIs and gives a chronological view of extractor activity.

Example prompt: Fetch the run feed for extractor ext-prices and report the timestamp of the most recent successful run.

### Agent Trigger on New Run

An agent that needs to act when a new crawl run completes can read the RSS feed periodically and detect new run entries. When a new run appears, the agent calls the data API to fetch the latest results and continues its workflow.

Example prompt: Poll the RSS feed for extractor ext-news every 10 minutes; when a new run id appears, fetch the latest JSON from the Data API.

### Run Auditing and Reporting

Compliance and BI teams can build a run audit log by archiving the RSS feed for each extractor on a regular schedule. The chronological feed makes it straightforward to compute run frequency, gaps, and failure clusters over time.

Example prompt: Pull the RSS feed for extractor ext-jobs and append any new entries to the audit table run_log.

### Jentic Watcher Agent

Through Jentic, an agent searches for the runs feed operation and watches an extractor without writing direct API code. Jentic injects the apikey and the agent only needs the extractor id to start watching.

Example prompt: Search Jentic for 'feed of extractor runs', load the schema, and execute with extractor id ext-jobs-board.

## Key resources

- **Run Feed** — RSS feed describing recent crawl runs for a specific extractor

## Why Jentic

- **Setup:** Wiring the import.io RSS API by hand means passing your apikey as a query parameter on every call and pointing at the dedicated rss.import.io host rather than the run or schedule hosts. Through Jentic you install once, import the import.io RSS API from the API Directory, store the apikey once, and your agent calls it.
- **Permission scoping:** This API is read-only monitoring: it exposes a single feed of extractor run history and nothing that starts crawls or fetches result rows. You choose the operations your agent may call, so a rule can limit it to reading that run feed and add no write operations, since none exist here.
- **Credential handling:** Your import.io apikey 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 'feed of extractor runs', and Jentic returns the import.io RSS operation with its input schema so the agent supplies the extractor id and calls the right endpoint without browsing the reference docs.

## Related APIs

- **import.io Run API** — Starts and cancels crawl runs that the RSS feed later reports
- **import.io Data API** — Reads the latest stored crawl results once a run completes
- **Apify** — Web scraping platform with native run lifecycle webhooks rather than RSS

## FAQ

### What authentication does the import.io RSS API use?

The RSS API uses an apikey query parameter on every request. Through Jentic, the apikey is stored in the encrypted vault and injected at runtime so the raw key never appears in agent prompts.

### Can I monitor runs for an extractor with this API?

Yes. GET `/extractor/{extractorId}/runs` returns a feed of recent crawl runs for the specified extractor. The feed is the supported way to track run activity without continuously polling the run or data APIs.

### What are the rate limits for the import.io RSS API?

The published spec does not declare hard rate limits. RSS feeds are typically polled rather than streamed, so reasonable polling intervals (every few minutes) avoid throttling at any plan tier.

### How do I subscribe to extractor run notifications through Jentic?

Search Jentic for 'feed of extractor runs' to find the operation backed by GET `/extractor/{extractorId}/runs.` Load the schema, pass the extractor id, and execute on a schedule. Jentic injects the apikey at runtime.

### How is RSS different from the Run API?

The Run API starts and cancels crawl runs. The RSS API only describes runs that have already happened. Pair them: Run kicks off work, RSS reports completion, and the Data API exposes the resulting rows.

### Can I limit what my agent is allowed to do with the import.io RSS API?

Yes. Because you run Jentic One yourself, you decide which operations your agent may call, and your own rules govern which credentials it uses. This API is read-only: its single operation, GET `/extractor/{extractorId}/runs`, returns a feed of an extractor's recent crawl runs and cannot start crawls or fetch result rows. So you can scope the agent to reading that run feed alone, and there are no write operations here for it to reach.