Turn any public web page into structured JSON with a plain-language instruction. Every numeric answer comes with a validation block that checks it against the page text and its history.
Run in Postman
{
"data": [
{
"value": "4010.00",
"raw_text": "4,010.00"
}
],
"validation": {
"status": "ok",
"reason": "no_reference",
"value": 4010,
"model_value": 4010,
"raw_text": "4,010.00",
"reference": null,
"change_pct": null,
"suspect_pct": 10,
"reject_pct": 30,
"on_page": true,
"votes": [],
"mode": "shadow",
"reference_source": null
}
}
curl --location --request GET 'https://zylalabs.com/api/14425/web+page+data+api/36431/extract+from+page?url=https://www.investing.com/commodities/gold&parse_description=Current gold futures price as a plain number, in a field called value&expiration_seconds=600&raw_text=true&value_field=value&last_value=4012.5&max_chars=6000' --header 'Authorization: Bearer YOUR_API_KEY'
{
"data": [
{
"value": 4066.5
}
],
"validation": {
"status": "ok",
"reason": "no_reference",
"value": 4066.5,
"model_value": 4066.5,
"raw_text": null,
"suspect_pct": 10,
"reject_pct": 30,
"on_page": null,
"votes": [],
"mode": "shadow"
}
}
curl --location --request GET 'https://zylalabs.com/api/14425/web+page+data+api/36432/extract+from+screenshot?url=https://www.investing.com/commodities/gold&llm_instructions=Current gold price in USD as a number, in a field called value&expiration_seconds=600&value_field=value&last_value=4012.5' --header 'Authorization: Bearer YOUR_API_KEY'
After signing up, every developer is assigned a personal API access key, a unique combination of letters and digits provided to access to our API endpoint. To authenticate with the Web Page Data API simply include your bearer token in the Authorization header.
| Header | Description |
|---|---|
Authorization
|
Required
Should be Bearer access_key. See "Your API Access Key" above when you are subscribed.
|
No long-term commitment. Upgrade, downgrade, or cancel anytime.
(Save 2 months with annual billing 🎉)
Web Page Data API turns any public web page into structured JSON. Send a URL and say in plain language what you need, for example current gold futures price as a number, in a field called value. The service fetches the page, prunes it, asks a large language model for exactly those fields and returns them as JSON.
Language models misread pages: they drop a decimal point (27015 instead of 270.15), pick a neighbouring row, or echo a number from the instruction. Every numeric answer is therefore checked before it is returned:
last_value if you send yours).The result comes in a validation object: status (ok, suspect, rejected or unchecked), reason, raw_text exactly as written on the page, on_page, and the thresholds used. The check is informational: you always receive the answer and decide what to do with it. The same pipeline runs in production on hundreds of thousands of extractions per month for commodity, metal and index prices.
Both accept an optional cache window (expiration_seconds, default 10 minutes), your own reference value (last_value) and the name of the field that holds the number when the answer has several (value_field).
Request: the URL of a gold futures quote page and parse_description=Current gold futures price as a plain number, in a field called value
{
"data": [{ "value": "4010.00", "raw_text": "4,010.00" }],
"validation": {
"status": "ok", "reason": "no_reference",
"value": 4010.0, "raw_text": "4,010.00", "on_page": true,
"suspect_pct": 10.0, "reject_pct": 30.0
}
}Name the fields you want back and be specific about which number: "the Last Price in the quote header, keeping its decimal point, in a field called value" works better than "the price". Do not put example numbers or ranges in the instruction: if the data is missing, a model tends to return the example.
A JSON object with two parts: data, the fields you asked for in your instruction, and validation, a check of the main numeric value (status ok, suspect, rejected or unchecked, the reason, the raw text as written on the page and the thresholds used).
In plain language, through parse_description (text endpoint) or llm_instructions (screenshot endpoint). Name the fields you want back, for example "product name, price in USD as a number and availability, in fields called name, price and in_stock".
Use Extract From Page by default: it is faster and works on the page text. Switch to Extract From Screenshot when the data only shows once the page is rendered, such as charts, widgets, canvas tables or JavaScript-heavy apps.
Whether the number is actually written on the page (on_page), whether it looks like a decimal shift (x10, x100), and how far it moved from the last accepted value for the same URL and instruction. You always receive the answer; the status tells you how much to trust it.
Yes. Send last_value with the last number you stored for that URL and instruction and the validation compares against it instead of the service history. Use value_field when your answer has several numbers.
No. The page and the answer are reused for the same URL and instruction while they are younger than expiration_seconds (default 600 seconds). Send 0 to force a fresh fetch.
Extract From Page reads the server-rendered text. For content that only appears after the page runs its scripts, use Extract From Screenshot, which renders the page in a browser before reading it.
The response comes with error true and a message describing the problem (blocked page, timeout, upstream error). The call is not counted as successful.
Both endpoints return structured JSON data. The Extract From Page endpoint provides fields based on the page's text, while the Extract From Screenshot endpoint returns data derived from rendered visuals, such as charts or widgets.
The key fields include "data," which contains the extracted values, and "validation," which provides the status of the extraction, reason for that status, and checks against the page text and historical values.
The response is organized into two main sections: "data," which holds the extracted information, and "validation," which details the accuracy checks performed on numeric values, including status and reasons for any discrepancies.
Extract From Page can retrieve text-based data like prices and specifications, while Extract From Screenshot is suited for visual data that requires rendering, such as graphs or dynamic content from JavaScript-heavy pages.
Users can customize requests by specifying the "parse_description" for Extract From Page or "llm_instructions" for Extract From Screenshot, detailing the exact fields they want, such as "current price" or "availability."
The data is sourced directly from public web pages. The API fetches the content and processes it using a language model or vision model, ensuring that the information is derived from the actual text or rendered visuals on the page.
A validation layer checks numeric values against the page text, historical values, and potential decimal shifts. The extracted value is always returned, and the status indicates the confidence in that value.
Typical use cases include price monitoring for commodities, competitor analysis, extracting product specifications, and feeding real-time data into AI systems, allowing for dynamic decision-making based on the extracted information.
To obtain your API key, first sign in to your account and navigate to the API you want to use. From the API's Pricing section, choose a plan and complete the subscription process. Once subscribed, return to the API page and you will see your API Access Key displayed at the top of the documentation page. You can use this key to authenticate your requests.
You can’t switch APIs during the free trial. If you subscribe to a different API, your trial will end and the new subscription will start as a paid plan.
The free trial lasts for 7 days and allows you to make up to 50 API requests.
No, the free trial is available only once, so we recommend using it on the API that interests you the most. Most of our APIs offer a free trial, but some may not include this option.
Yes. If the API offers a free trial, you will see a "Free 7-Day Trial" option in its Pricing section. The trial lasts for 7 days and allows up to 50 API requests, enabling you to evaluate the API before subscribing to a paid plan.
Zyla API Hub is like a big store for APIs, where you can find thousands of them all in one place. We also offer dedicated support and real-time monitoring of all APIs. Once you sign up, you can pick and choose which APIs you want to use. Just remember, each API needs its own subscription. But if you subscribe to multiple ones, you'll use the same key for all of them, making things easier for you.
You can monitor your API usage through the response headers included with every request:
x-zyla-api-calls-monthly-used: Shows the total number of API requests you have used during the current billing period.
x-zyla-api-calls-monthly-remaining: Shows the number of API requests you have remaining for the current billing period.
Yes, you can cancel your subscription at any time. Simply go to the Pricing section of the API you're subscribed to and click the "Unsubscribe" button.
Please note that upgrades, downgrades, and cancellations take effect immediately. Once your subscription is canceled, access to the service will end immediately, regardless of any remaining API calls in your quota.
Please have a look at our Refund Policy: https://zylalabs.com/terms#refund
