You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+119-2Lines changed: 119 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,13 +2,14 @@
2
2
3
3
Turn any website into a REST API by scraping it live with Playwright.
4
4
5
-
Web2API loads recipe folders from `recipes/` at startup. Each recipe defines endpoints with selectors, actions, fields, and pagination in YAML. Optional Python scrapers handle interactive or complex sites. Drop a folder — get an API.
5
+
Web2API loads recipe folders from `recipes/` at startup. Each recipe defines endpoints with selectors, actions, fields, and pagination in YAML. Optional Python scrapers handle interactive or complex sites. Optional plugin metadata can declare external dependencies and required env vars. Drop a folder — get an API.
6
6
7
7
## Features
8
8
9
9
-**Arbitrary named endpoints** — recipes define as many endpoints as needed (not limited to read/search)
10
10
-**Declarative YAML recipes** with selectors, actions, transforms, and pagination
11
11
-**Custom Python scrapers** for interactive sites (e.g. typing text, waiting for dynamic content)
12
+
-**Optional plugin metadata** (`plugin.yaml`) for recipe-specific dependency requirements
12
13
-**Shared browser/context pool** for concurrent Playwright requests
13
14
-**In-memory response cache** with stale-while-revalidate
14
15
-**Unified JSON response schema** across all recipes and endpoints
0 commit comments