Nedradv APInedradv.ru ↗
Access Russia's Nedradv mineral deposit database via API. List deposits by mineral type or region, and retrieve reserves, geological conditions, and location data.
What is the Nedradv API?
The Nedradv.ru API provides structured access to Russia's mineral deposit registry through 2 endpoints, returning deposit listings and detailed reserve records. Use list_deposits to browse or filter the database by mineral type and region, then call get_deposit with a 32-character hex ID to retrieve 8 fields of deposit-level detail including reserves by exploration degree, geological conditions, and information source references.
curl -X GET 'https://api.parse.bot/scraper/c39b82e2-24b5-4029-a4bf-f9426e68fddf/list_deposits?page=1®ion=853d7f00177439bd602cfe5ff200ac01&mineral=ea137769ab1dc8b338a79c54c3009281' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace nedradv-ru-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: nedradv SDK — bounded, re-runnable; every call capped."""
from parse_apis.nedradv_ru_api import Nedradv, DepositNotFound
client = Nedradv()
# List all deposits, capped at 3 items
for deposit in client.deposits.list(limit=3):
print(deposit.id, deposit.name)
# Drill-down: get first deposit details
item = client.deposits.list(limit=1).first()
try:
full = client.deposits.get(id=item.id)
print(full.name, full.mineral_type, full.region)
print("Reserves:", full.reserves[:100])
except DepositNotFound as e:
print("not found:", e.id)
# Navigate from summary to full details via .details()
for summary in client.deposits.list(limit=2):
detail = summary.details()
print(detail.name, detail.mineral_type, detail.location[:60])
print("exercised: deposits.list, deposits.get, DepositSummary.details")
List mineral deposits from the Nedradv database. Returns paginated results (200 per page, up to 25 pages). Optionally filter by mineral type ID or region ID. Results are auto-iterated across pages.
| Param | Type | Description |
|---|---|---|
| page | integer | Page number (1-based). Each page returns up to 200 deposits. |
| region | string | Region ID to filter deposits (32-character hex). When set, only deposits in that region are returned. |
| mineral | string | Mineral type ID to filter deposits (32-character hex, e.g. from the mineral filter on the site). When set, only deposits of that mineral type are returned. |
{
"type": "object",
"fields": {
"page": "current page number",
"count": "number of deposits on this page",
"deposits": "array of deposit summaries with id and name",
"total_pages": "total number of pages available"
},
"sample": {
"data": {
"page": 1,
"count": 200,
"deposits": [
{
"id": "f2f5e2370b07304ef3b5b8e491532f3d",
"name": "Абановское газовое месторожден..."
}
],
"total_pages": 25
},
"status": "success"
}
}About the Nedradv API
Endpoints and What They Return
The list_deposits endpoint returns paginated summaries of mineral deposits from the Nedradv database. Each page holds up to 200 deposits, and the database spans up to 25 pages of results. Each deposit summary includes an id and name. You can narrow results using a region parameter (a 32-character hex region ID) or a mineral parameter (a 32-character hex mineral type ID) — both are optional and can be combined. The response also includes page, count, and total_pages fields for iteration.
Deposit Detail
The get_deposit endpoint accepts a single required input — the 32-character hex id obtained from list_deposits — and returns the full deposit record. Fields include name, region (region and administrative district), location (a geographic description), mineral_type, reserves (broken down by degree of geological exploration), geological_conditions (mining and technical conditions), notes, and info_source (the bibliographic or document reference for the deposit data). This makes it suitable for structured extraction of reserve specifications without manual lookup.
Coverage and Scope
The database covers mineral deposits across Russian regions as catalogued on nedradv.ru. Filtering is available at the region and mineral-type level; no sub-region or commodity-quantity range filter is exposed. Deposits are identified by opaque hex IDs, so a typical workflow starts with list_deposits (optionally filtered) to collect IDs, followed by individual get_deposit calls for full records.
The Nedradv API is a managed, monitored endpoint for nedradv.ru — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when nedradv.ru 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 nedradv.ru 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?+
- Build a searchable index of Russian mineral deposits filtered by commodity type using the
mineralparameter - Compare reserve figures across deposits in a specific region by combining the
regionfilter withget_depositcalls - Extract
geological_conditionsfields in bulk to assess mining feasibility across a commodity class - Populate a GIS or mapping tool with deposit
locationandregiondata from the full deposit list - Track
info_sourcereferences to cross-check deposit data against regulatory filings or geological surveys - Aggregate
mineral_typeandreservesfields to build commodity-level inventory summaries by Russian region
| 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 nedradv.ru offer an official developer API?+
What does the `reserves` field in `get_deposit` contain?+
reserves field returns reserve data broken down by degree of geological exploration — the classification system used in Russian mineral resource accounting (categories such as A, B, C1, C2). The specific values and units reflect what is recorded in the Nedradv source entry for that deposit.How do I find valid `region` and `mineral` filter IDs for `list_deposits`?+
list_deposits without filters first, collect deposit IDs, inspect get_deposit responses for region and mineral_type values, and match those against the filter options visible on the Nedradv site to identify the corresponding hex IDs.Does the API return coordinates or map geometry for deposits?+
location field with a geographic description and a region field with the administrative district, but no latitude/longitude coordinates or geometry are exposed. You can fork this API on Parse and revise it to add coordinate extraction if that data becomes available in deposit records.Is there a limit to how many deposits can be retrieved in total?+
list_deposits returns up to 200 deposits per page and supports up to 25 pages, for a maximum of 5,000 deposit records per query configuration. Applying region or mineral filters will reduce the result set. If a filtered query returns fewer than 25 pages, total_pages in the response reflects the actual count.