Browse the Gallery
Explore pre-built templates for popular sites — no coding required
Install Plugin
Use Nimble directly in Claude Code or Cursor
Quick Start
Example Request
Example Response
How it works
1
Select a template and provide inputs
Choose a template by name (e.g.,
amazon_pdp, google_search) and pass the
required parameters like product ID, search query, or URL2
Nimble handles everything
The template fetches the page, handles anti-bot protection, and extracts data
using battle-tested selectors maintained by Nimble
3
Receive structured data
Get clean, normalized JSON with consistent field names - ready to use in
your application immediately
Every template. One API.
Every template works through the same simple API. Pick a site, pass its parameters, and get production-ready structured data.Pre-Built Templates
A growing library of templates for popular websites — maintained by Nimble
24/7, auto-healing when sites change. Browse the
Gallery.
Nimble Plugin
Use templates directly from your IDE with the Nimble
plugin in Claude Code or
Cursor.
Parameters
Supported input parameters:template - Required
template - Required
The name of the template to use. Each template is designed for a specific platform or data type.Popular templates:
amazon_pdp- Amazon product pagesamazon_serp- Amazon search resultsgoogle_search- Google search resultsgoogle_maps_search- Google Maps locationswalmart_pdp- Walmart productschatgpt- ChatGPT prompt resultsperplexity- Perplexity prompt results
params - Required
params - Required
Template-specific parameters that tell the template what data to fetch. Each template has different requirements.Common param types:
- Product IDs (ASINs, SKUs)
- Search queries
- URLs or usernames
- Page numbers for pagination
params also accepts the following Extract API parameters:country- Country used to access the target URL. Use ISO Alpha-2 codes.locale- Language preference for the results. Use the LCID standard.tag- User-defined tag for request identification.parse- Whether to enable or disable parsing. Enabled by default.
localization
localization
Enable location-based pricing and availability. Required when passing
zip_code or store_id in params.Only available for templates that support localization (check template details).Example:formats
formats
Output formats to include in the response alongside
data.parsing. By default, only structured parsed data is returned.Available formats:html- Raw HTML source of the extracted pagemarkdown- Clean markdown version of the pageheaders- HTTP response headers as a key-value object underdata.headerslinks- All URLs found on the page as an array underdata.links
Usage
E-commerce product extraction
Extract product data from Amazon, Walmart, and other retailers:Search results extraction
Get search results from Google, Amazon, and other platforms:Google Maps extraction
Find businesses and locations:LLM platform extraction
Get responses from AI platforms like ChatGPT and Perplexity:Extraction with Localization
Use thelocalization parameter to get location-specific pricing and availability. Pass a zip_code or store_id in params to target a specific locale.
Pagination
Some templates support pagination — check the template’s input properties for a field withis_pagination_param: true, or feature_flags.is_pagination_supported: true on the template metadata.
Pagination is client-driven: call the template once per page by incrementing the pagination field (commonly page) in params. Nimble does not return a “last page” signal — you decide when to stop.
Example: Paginate Amazon search results
Theamazon_serp template accepts a page parameter. Call the template once per page, incrementing page each run. The example below fetches 10 pages of results for the keyword iphone 17.
Remember to validate results page-by-page — some sites return placeholder
content for pages beyond the real total instead of an empty response.
Async & Batch
Run template extractions in the background or submit multiple template requests at once. Both modes return immediately with a task or batch ID — no waiting while Nimble processes the work.- Async Example
- Batch Example
- Run templates without blocking your application
- Process multiple template requests in parallel
- Deliver results to cloud storage (S3 / GCS) automatically
- Receive webhook notifications when tasks complete
- Integrate templates into scheduled or queued workflows
How it works
1
Submit a request
Send a POST request to the async or batch endpoint. The API returns
immediately with a
task_id (async) or batch_id (batch) — no waiting for
the template to finish.2
Nimble processes in the background
The template runs asynchronously. For batch, each input becomes an independent
task processed in parallel.
3
Receive results your way
Choose how results are delivered:
- Polling — check task status and fetch results on demand
- Webhook — get notified automatically when a task completes
- Cloud storage — results saved directly to your S3 or GCS bucket
Async
Submit a single template request and receive atask_id immediately. Retrieve results via polling, webhook, or cloud storage.
Parameters
Accepts all Template parameters, plus async-specific delivery options:template(required) — The template to runparams(required) — Template-specific input parameterslocalization— Enable location-based dataformats— Output formats:html,markdown,headers
storage_type
storage_type
Storage provider for results. When specified, results are saved to your cloud storage instead of Nimble’s servers.Options:
s3 (Amazon S3), gs (Google Cloud Storage)storage_url
storage_url
Bucket path where results will be saved. Results are stored as
{task_id}.json at the specified location.Format: s3://your-bucket/path/prefix/storage_compress
storage_compress
Compress results with GZIP before saving. When
true, results are saved as {task_id}.json.gz.storage_object_name
storage_object_name
Custom filename for the stored object instead of the default task ID.Example:
"my-custom-name" saves as my-custom-name.jsoncallback_url
callback_url
Webhook URL to receive a POST request when the task completes. Nimble sends task metadata (without result data) to this URL when the template finishes.Example:
https://your-api.com/webhook/completeStatus & Results
When polling, the typical flow is:- Poll
GET /v2/tasks/{task_id}untilstate: "success" - Call
GET /v2/tasks/{task_id}/resultsto retrieve the extracted data
Batch
Submit up to 1,000 template requests in a single request. Each input runs as an independent async task. Useshared_inputs to set the template and common settings — individual items in inputs can override params per item.
Parameters
inputs — Required
inputs — Required
Array of per-item inputs. Supports up to 1,000 items per batch.
template is not set here — it must be in shared_inputs and applies to all items.Each item supports:params— Template-specific inputs for this item (e.g.asin,keyword). Merged withshared_inputs.params— keys ininputs[i].paramstake priority on conflicts.localization— Override the shared localization setting for this itemformats— Override the shared formats setting for this item
Examples
Example 1: Batch multiple keywords
Example 1: Batch multiple keywords
Run the same template for multiple search terms with S3 delivery:
Example 2: Batch multiple product ASINs
Example 2: Batch multiple product ASINs
Extract product details for many ASINs at once:
batch_id and the initial task list:
Status & Results
When polling, the typical flow is:- Poll
/v2/batches/{batch_id}/progressuntilcompleted: true - Fetch
/v2/batches/{batch_id}to get all task IDs and states - For each
successtask, callGET /v2/tasks/{task_id}/results
1
Poll for batch completion
Call/v2/batches/{batch_id}/progress repeatedly until completed: true. This is a lightweight endpoint — use it for polling.2
Fetch the full batch details
Oncecompleted: true, fetch the batch details to get all task IDs, states, and download URLs.3
Retrieve results per task
Iterate over the task list and callGET /v2/tasks/{task_id}/results for each success task.Template Gallery
Browse pre-built templates maintained by Nimble for popular platforms:Explore Full Gallery
Browse all templates with interactive documentation and live testing
E-commerce
Search Engines
LLM Platforms
Social Media
Response Fields
Use cases
Price Monitoring
Track prices across Amazon, Walmart, and other retailers with consistent
data formats
Product Research
Gather comprehensive product data from major e-commerce platforms
Search Tracking
Monitor Google, Bing, and marketplace search results for SEO and visibility
Competitive Intelligence
Extract competitor data from popular sites using pre-built templates
Templates vs other tools
Next steps
Browse the Gallery
Explore pre-built templates for popular sites
Install Plugin
Use Nimble in Claude Code or Cursor — your AI assistant builds requests for
you
Extract
Full control with CSS selectors and parsing schemas
Callbacks & Delivery
Deliver async and batch results to your storage or webhook