DeviceSpecifications APIdevicespecifications.com ↗
Access mobile device specs, brand listings, model indexes, and filtered search across thousands of phones and tablets via the DeviceSpecifications.com API.
What is the DeviceSpecifications API?
The DeviceSpecifications.com API covers 4 endpoints that expose brand listings, device model indexes, full specification sheets, and a filtered device search. Call get_device_details to retrieve specs organized into named categories — Design, Display, Battery, Camera, and more — for any device identified by its model ID. The API supports programmatic traversal from brand to model to spec without any manual lookup.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/0ba9e915-4cb3-4d1a-b73c-80419113783e/get_brands' \ -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 devicespecifications-com-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.
from parse_apis.devicespecifications_api import DeviceSpecifications, SocManufacturer
client = DeviceSpecifications()
# List all brands
for brand in client.brands.list(limit=5):
print(brand.name, brand.id)
# Browse devices under a brand using constructible access
apple = client.brand("cefa26")
for device in apple.devices.list(limit=3):
print(device.name, device.url)
# Navigate to full specifications
detail = device.details()
print(detail.name, detail.model_id)
for category, specs in detail.specifications.items():
print(category)
# Search for Qualcomm-powered devices with 5G
for result in client.devicesummaries.search(select_soc=SocManufacturer.QUALCOMM, five_g="1", ram="8", limit=10):
print(result.name, result.id)
# Get a device directly by model_id
phone = client.devices.get(model_id="d6bd677d")
print(phone.name, phone.model_id)
Retrieve all mobile device brands listed on the site. Each brand includes a hex identifier that can be used with other endpoints to fetch its devices. No parameters required; always returns the complete brand catalog.
No input parameters required.
{
"type": "object",
"fields": {
"brands": "array of brand objects with id, name, url, and image_url"
},
"sample": {
"data": {
"brands": [
{
"id": "6b2c3a",
"url": "https://www.devicespecifications.com/en/brand/6b2c3a",
"name": "Acer",
"image_url": null
},
{
"id": "cefa26",
"url": "https://www.devicespecifications.com/en/brand/cefa26",
"name": "Apple",
"image_url": null
},
{
"id": "d1cd1",
"url": "https://www.devicespecifications.com/en/brand/d1cd1",
"name": "Samsung",
"image_url": null
}
]
},
"status": "success"
}
}About the DeviceSpecifications API
Browsing Brands and Models
The get_brands endpoint returns every mobile device brand on DeviceSpecifications.com as an array of objects, each with an id, name, url, and image_url. Pass any brand's id to get_brand_devices to retrieve that brand's full device roster — same object shape: id, name, url, and image_url per device. The brand_id you queried is echoed back in the response, which is useful when batching requests across multiple brands.
Device Specification Detail
The get_device_details endpoint accepts a model_id (a hex string obtained from get_brand_devices or search_devices) and returns the full device name, the queried model_id, and a specifications object. That object uses category names — such as Design, Display, Battery, Camera, Connectivity — as keys, each mapped to a flat set of spec key-value pairs. The structure is consistent across devices, making it straightforward to extract a specific attribute like screen resolution or battery capacity programmatically.
Filtered Device Search
The search_devices endpoint accepts up to five optional filter parameters: 5g (require 5G support), ram, battery (minimum capacity), storage, and select_soc (SoC manufacturer, e.g. qualcomm, apple, mediatek). Omitting all filters returns the most recent devices. Results include a total count and an array of matching devices with id, name, and url. Use returned id values as model_id inputs to get_device_details to fetch full specs for each match.
Data Coverage and IDs
All entity identifiers — brand IDs and model IDs — are opaque hex strings. They are stable references intended to be passed between endpoints; the get_brands → get_brand_devices → get_device_details chain is the canonical traversal pattern. The search endpoint is a parallel entry point that bypasses the brand hierarchy when you already know the hardware criteria you need.
The DeviceSpecifications API is a managed, monitored endpoint for devicespecifications.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when devicespecifications.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 devicespecifications.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?+
- Build a device comparison tool by fetching
specificationsfor multiple model IDs and diffing Display or Camera categories. - Populate a product database with structured specs by iterating
get_brands→get_brand_devices→get_device_details. - Filter devices by SoC manufacturer using
select_socinsearch_devicesto benchmark Qualcomm vs. MediaTek chipsets. - Generate a 5G-capable device list with minimum 8 GB RAM by combining the
5gandramfilters insearch_devices. - Automate spec sheet generation for a review site by querying
get_device_detailsfor each model at publication time. - Track a brand's full device catalog by calling
get_brand_deviceswith the brand's hex ID fromget_brands. - Feed a recommendation engine with battery and storage capacities extracted from the
specificationsobject.
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does DeviceSpecifications.com offer an official developer API?+
What does `get_device_details` return and how are specs organized?+
name, the queried model_id, and a specifications object. The keys of that object are category names (e.g. Display, Battery, Camera, Design) and each category maps to a flat set of attribute-value pairs for that device.What filters does `search_devices` support?+
5g (pass '1' to require 5G), ram, battery (minimum capacity), storage, and select_soc (manufacturer slug like 'qualcomm' or 'mediatek'). All parameters are optional and default to no filter when omitted or set to '-'.Does the API support pagination for large brand catalogs or search results?+
get_brand_devices returns all devices for a brand in one response, and search_devices returns all matching results with a total count but no page or offset controls. You can fork this API on Parse and revise it to add paginated endpoints if your use case requires chunked retrieval.