Neiman APIneiman.com ↗
Access structured company data for Neiman Enterprises via one API endpoint: products, locations, certifications, facility profiles, and founding details.
What is the Neiman API?
The Neiman Enterprises API exposes a single get_company_profile endpoint that returns 8 structured fields covering the lumber company's full public profile — including named product lines with descriptions, geocoded facility locations, sustainability certifications with scope statements, and founding history. Every returned fact includes a source_url pointing to the originating page on neiman.com, making the response fully auditable.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/400f74fe-a002-45b0-8553-7dfe291b6577/get_company_profile' \ -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 neiman-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.
"""Walkthrough: Neiman Enterprises company profile — typed access to every section."""
from parse_apis.neiman_com_api import NeimanCom, ParseError
client = NeimanCom()
# Fetch the full company profile (single object, no parameters).
try:
profile = client.company_profiles.get()
except ParseError as e:
print("Extraction failed:", e.code)
raise
print(profile.company_name, profile.website)
# Founding details (nullable — guard before access).
if profile.founding is not None:
print(f"Founded {profile.founding.year} in {profile.founding.place}")
# Walk products offered.
for product in profile.products:
print(product.name, product.source_url)
# Walk facility locations from the contact page.
for loc in profile.locations:
print(loc.name, loc.city, loc.state, loc.phone)
# Certifications held by the company.
for cert in profile.certifications:
print(cert.name, cert.scope)
# Facility-level profiles with per-mill product lists.
for facility in profile.facility_profiles:
print(facility.name, facility.city, facility.state, facility.products)
print("exercised: company_profiles.get")
Returns one company profile object for Neiman Enterprises built from the live website: company name, website, description (about-page paragraphs), founding statement, products (one object per product page linked from the products page, with the page's own description), locations (every facility listed on the contact page's location map: name, city, state, full address, phone, coordinates), certifications (only certifications the sustainability page explicitly states; scope names the entity the site attributes it to), and facility_profiles (a facility appears only when a product page explicitly names that facility or its city/state; products and description are restricted to those explicit statements, so group-wide products, certifications and locations are never assigned to an individual mill). Takes no parameters. About ten page fetches per call. Unknown values are null; unknown lists are empty arrays. source_urls lists every page read.
No input parameters required.
{
"type": "object",
"fields": {
"website": "canonical site URL",
"founding": "object {year, place, source_url} from the site's founding statement, or null",
"products": "array of {name, description, source_url}, one per product page",
"locations": "array of {name, city, state, address, phone, latitude, longitude, source_url} from the contact-page location map",
"description": "about-page description text, or null",
"source_urls": "array of every page URL read to build the profile",
"company_name": "company name as written on the site",
"certifications": "array of {name, scope, statement, source_url}; scope is the entity the site attributes the certification to",
"facility_profiles": "array of {name, city, state, products, description, source_url, source_urls}, only for facilities explicitly named in product statements"
},
"sample": {
"data": {
"website": "https://www.neiman.com",
"founding": {
"year": 1936,
"place": "Upton, Wyoming",
"source_url": "https://www.neiman.com/about"
},
"products": [
{
"name": "Premium Studs",
"source_url": "https://www.neiman.com/premium-studs",
"description": "Wood studs are a essential component of any construction project ... The no-prior select Premium ESLP (Engelmann Spruce Lodgepole Pine) studs produced at Montrose Forest Products are suitable for many applications."
}
],
"locations": [
{
"city": "Montrose",
"name": "Montrose Forest Products",
"phone": "+1 (555) 012-3456",
"state": "Colorado",
"address": "11925 6530 Rd, Montrose, Colorado, 81401",
"latitude": 38.52304628,
"longitude": -107.87415862,
"source_url": "https://www.neiman.com/contact"
}
],
"description": "We're committed to timber production practices driven by forest health. ... since our first mill opened in 1936 in Upton, Wyoming.",
"source_urls": [
"https://www.neiman.com/",
"https://www.neiman.com/about",
"https://www.neiman.com/products",
"https://www.neiman.com/contact",
"https://www.neiman.com/sustainability",
"https://www.neiman.com/premium-studs"
],
"company_name": "Neiman Enterprises",
"certifications": [
{
"name": "SFI (Sustainable Forestry Initiative) certification",
"scope": "Neiman Enterprises",
"statement": "Neiman Enterprises SFI Certificate",
"source_url": "https://www.neiman.com/sustainability"
}
],
"facility_profiles": [
{
"city": "Montrose",
"name": "Montrose Forest Products",
"state": "Colorado",
"products": [
"Premium Studs"
],
"source_url": "https://www.neiman.com/premium-studs",
"description": "The no-prior select Premium ESLP (Engelmann Spruce Lodgepole Pine) studs produced at Montrose Forest Products are suitable for many applications.",
"source_urls": [
"https://www.neiman.com/premium-studs"
]
}
]
},
"status": "success"
}
}About the Neiman API
What get_company_profile Returns
The get_company_profile endpoint returns one company profile object assembled from multiple pages of neiman.com. The top-level fields include company_name, website, description (the about-page text), and a founding object with year, place, and source_url. The source_urls array lists every page read to build the response, so you can trace exactly which sections of the site contributed to the output.
Products and Facilities
The products array contains one object per product page linked from the products section of the site. Each object carries name, description, and source_url. Closely related, facility_profiles goes deeper: each entry includes name, city, state, a products array, a description, and both source_url and source_urls fields for facilities that are explicitly named in product-related content. This lets you cross-reference which physical mills or yards produce which product lines.
Locations and Certifications
The locations array is drawn from the contact-page location map and includes name, city, state, address, phone, latitude, and longitude per entry — all with a source_url. The certifications array covers sustainability and quality certifications the site discloses, with name, scope (the entity the site attributes the certification to), statement, and source_url. If the site lists no certifications, the array is empty rather than null.
No Parameters Required
get_company_profile takes no inputs. There is no filtering, pagination, or query string. The endpoint always returns the full profile object in a single call.
The Neiman API is a managed, monitored endpoint for neiman.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when neiman.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 neiman.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?+
- Populating a supplier database with Neiman Enterprises' verified product lines and facility locations
- Monitoring changes to the company's sustainability certifications and their attributed scope
- Building a B2B directory entry that includes geocoded mill/yard addresses and phone numbers
- Auditing founding history and corporate description for due-diligence workflows
- Feeding a procurement tool with structured product names and descriptions from neiman.com
- Cross-referencing facility profiles with product lines to map production geography
| 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 Neiman Enterprises offer an official developer API?+
What does the locations array actually include, and does it cover all facility types?+
locations includes name, city, state, address, phone, latitude, longitude, and source_url, sourced from the contact-page location map. The facility_profiles array covers facilities named in product-related content and adds products and description fields. Locations not referenced in product content appear in locations but may not have a corresponding facility_profiles entry.Does the API return pricing, inventory levels, or purchase order data?+
How are certifications attributed when the site lists them at different levels?+
scope field that records the entity the site itself attributes the certification to — this could be the parent company, a specific mill, or a product line. The statement field captures the verbatim or paraphrased claim from the source page, and source_url links back to where it was found.Is there any way to retrieve only product data or only location data without the full profile?+
products, locations, certifications, and facility_profiles are all top-level keys in that one response. You can fork this API on Parse and revise it to add targeted endpoints that return only a subset of the profile.