Fidlar APIava.fidlar.com ↗
Search Rockingham County (NH) Registry of Deeds by book and page number. Returns deed records with document type, parties, dates, and legal descriptions.
What is the Fidlar API?
The ava.fidlar.com API provides access to recorded deed records in the Rockingham County, New Hampshire Registry of Deeds through a single endpoint, search_deeds_by_book_page. A search by book and page returns an array of matching deed records with up to 6 distinct data fields per record, including document type, party names, recording dates, and legal descriptions — without requiring a visit to the Registry office.
curl -X POST 'https://api.parse.bot/scraper/99dcdf7d-7054-4fc8-a887-e95dedbd8e49/search_deeds_by_book_page' \
-H 'X-API-Key: $PARSE_API_KEY' \
-H 'Content-Type: application/json' \
-d '{
"book": "5000",
"page": "100"
}'Search for recorded deeds by book and page number in the Rockingham County Registry of Deeds. Returns matching deed records including document type, parties, recording dates, legal descriptions, and notes. Each call makes two upstream requests (token + search) and solves an invisible reCAPTCHA v3 challenge.
| Param | Type | Description |
|---|---|---|
| bookrequired | string | Book number to search (numeric string, e.g. '5000'). |
| pagerequired | string | Page number within the book (numeric string, e.g. '100'). |
{
"type": "object",
"fields": {
"deeds": "Array of deed records matching the book/page query",
"total_results": "Total number of matching deed records"
},
"sample": {
"data": {
"deeds": [
{
"book": "5000",
"page": "100",
"notes": "4157-1010",
"legals": [],
"party1": "DEWING BARBARA J KEARNEY ETAL ",
"party2": null,
"parties": [
{
"name": "DEWING BARBARA J KEARNEY ETAL",
"party_type_id": 1,
"additional_name": null
},
{
"name": "DEWING JEROME B II ETAL",
"party_type_id": 1,
"additional_name": null
},
{
"name": "RBS CITIZENS NA",
"party_type_id": 3,
"additional_name": null
}
],
"document_date": "4/14/2009",
"document_type": "DISCH",
"legal_summary": "",
"document_number": "5000-0100",
"image_page_count": 1,
"reference_number": "",
"recorded_date_time": "4/14/2009 7:00:00 AM",
"consideration_amount": 0
}
],
"total_results": 1
},
"status": "success"
}
}About the Fidlar API
What the API Returns
The search_deeds_by_book_page endpoint accepts two required inputs — book (a numeric string identifying the deed book, e.g. '5000') and page (a numeric string identifying the page within that book, e.g. '100'). The response includes a deeds array of matching records and a total_results count. Each record in the array surfaces document type, party names (grantor and grantee), recording dates, legal descriptions of the property, and any associated notes.
Response Fields
Each deed record in the deeds array reflects what was filed at the time of recording: the document type (e.g. warranty deed, quitclaim deed), the names of the parties involved, the exact recording date, a legal description of the parcel, and clerk or processing notes. The total_results field tells you how many records matched the book-and-page query, which is useful when a single book/page combination references more than one instrument.
Coverage and Scope
This API is scoped specifically to Rockingham County, New Hampshire. Data corresponds to the official recorded instruments held at the Rockingham County Registry of Deeds. The book-and-page coordinate system is the canonical citation format used in New Hampshire land records, so this API fits naturally into title search workflows, chain-of-title analysis, and property research tools that already reference NH deeds by that notation.
The Fidlar API is a managed, monitored endpoint for ava.fidlar.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ava.fidlar.com changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official ava.fidlar.com API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Automating title chain lookups by iterating over book/page references found in prior deeds
- Pulling grantor and grantee party names from historical Rockingham County deeds for ownership history reports
- Verifying recording dates and document types for real estate transaction due diligence
- Populating a local property database with legal descriptions from NH Registry records
- Cross-referencing deed notes and instrument metadata for lien or encumbrance research
- Building an alert or audit tool that confirms specific book/page entries exist in the registry
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 200 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
| Team | $300/mo | 20,000 | 300 req/min |
| Company | $1,000/mo | 100,000 | 500 req/min |
Each endpoint has a fixed posted price per successful call — most fall between 1 and 10 credits — shown on this API's page before you run it. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does Fidlar / ava.fidlar.com offer an official developer API?+
What does the search_deeds_by_book_page endpoint return beyond basic deed identification?+
deeds array includes the names of the parties (grantor and grantee), a legal description of the property, and any notes attached to the instrument. The total_results field indicates how many records share that book-and-page reference.