Noomii APInoomii.com ↗
Access Noomii's professional coach directory via API. Search coaches by category and location, retrieve full profiles with bios, rates, and specialties.
What is the Noomii API?
The Noomii API exposes 4 endpoints covering the full Noomii professional coach directory — from category listings to individual coach profiles. Use search_coaches to query by category slug (e.g. life-coaches, business-coaches) and location, or call get_coach_profile to retrieve a single coach's complete biography, hourly rate, phone number, specialties, and Noomii score.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/c78d7ab5-7889-4f59-9bea-e21367a3c217/list_coach_categories' \ -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 noomii-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: Noomii coach directory — browse categories, search coaches, drill into profiles."""
from parse_apis.noomii_coach_directory_api import Noomii, CoachNotFound
client = Noomii()
# List all coaching categories to see what's available.
for category in client.categories.list(limit=5):
print(category.name, category.count)
# Construct a category by slug, then search for coaches in that category + location.
life = client.category(slug="life-coaches")
coach_summary = life.coaches.search(location_slug="california", limit=1).first()
if coach_summary:
print(coach_summary.name, coach_summary.noomii_score, coach_summary.review_count)
# Drill into the full profile from a summary.
full_profile = coach_summary.details()
print(full_profile.name, full_profile.location, full_profile.hourly_rate)
# Get location filter options for a category.
biz = client.category(slug="business-coaches")
for loc in biz.locations.list(limit=5):
print(loc.name, loc.location_slug, loc.count)
# Typed error handling: catch CoachNotFound for a bad slug.
try:
client.coaches.get(slug="nonexistent-coach-slug-xyz")
except CoachNotFound as exc:
print(f"Coach not found: {exc.slug}")
print("exercised: categories.list / category.coaches.search / coach_summary.details / category.locations.list / coaches.get")
Returns all available coach category types with their slugs and coach counts from the directory sidebar. One-page response; no pagination parameters.
No input parameters required.
{
"type": "object",
"fields": {
"categories": "array of category objects each containing name (string), slug (string), and count (integer)"
},
"sample": {
"data": {
"categories": [
{
"name": "ADD ADHD Coaches",
"slug": "add-adhd-coaches",
"count": 1016
},
{
"name": "Business Coaches",
"slug": "business-coaches",
"count": 3337
},
{
"name": "Career Coaches",
"slug": "career-coaches",
"count": 3750
}
]
},
"status": "success"
}
}About the Noomii API
What the API Covers
The Noomii API provides structured access to the Noomii coach directory across four endpoints. list_coach_categories returns every coach category available in the directory, including the category name, slug, and count of coaches listed — useful for building dynamic filter UIs or knowing which slugs to pass to other endpoints.
Searching and Filtering Coaches
search_coaches accepts a category_slug (defaulting to life-coaches if omitted), an optional location_slug, and a page integer for pagination. Each result in the coaches array includes the coach's name, slug, tagline, specialties, noomii_score, review_count, bio_excerpt, and location. The has_next boolean tells you whether additional pages exist. To get valid location_slug values for a given category, call get_location_filter_options with the same category_slug first — it returns US states and Canadian provinces with their coach counts.
Full Coach Profiles
get_coach_profile takes a slug from search results and returns the complete profile: bio, phone, location, hourly_rate (as a string range with currency), specialties array, website_url via Noomii redirect, and noomii_score. Fields like phone and website_url are included where the coach has provided them; noomii_score may return null if not available for that coach.
The Noomii API is a managed, monitored endpoint for noomii.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when noomii.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 noomii.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 coach-matching tool that filters by specialty category and US state or Canadian province using
search_coachesandget_location_filter_options. - Aggregate hourly rate data across coach categories to benchmark coaching market rates by region.
- Populate a CRM or lead database with coach contact details including phone and website URL from
get_coach_profile. - Display Noomii score and review count alongside coach bios to help users compare coaches programmatically.
- Generate category and location coverage reports using coach counts from
list_coach_categoriesandget_location_filter_options. - Build a career-services platform that surfaces relevant business or career coaches filtered by location slug.
- Monitor coach directory growth by periodically querying category counts and paginated search results.
| 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 Noomii have an official developer API?+
What does `get_coach_profile` return beyond what appears in search results?+
search_coaches returns a bio_excerpt, but get_coach_profile returns the full bio text along with additional fields not present in search results: phone, hourly_rate, and website_url. The noomii_score field is present in both but may be null if a coach has not yet received a score.How does location filtering work, and what locations are covered?+
get_location_filter_options returns location slugs for US states and Canadian provinces for a given category_slug. You pass the returned location_slug values (e.g. new_york, california, ontario) into search_coaches. Only locations with active coach listings appear in the results, so the available slugs vary by category.Does the API expose coach reviews or review text?+
review_count integer in search results, but individual review text and reviewer details are not currently exposed. The API covers profile data, categories, and location filters. You can fork it on Parse and revise to add a review-fetching endpoint.Is pagination supported across all search results, and are there any limits?+
search_coaches returns a page integer and a has_next boolean so you can iterate through all results for a given category and location. There is no explicit cap documented on pages, but results reflect the live directory state at the time of the request, so counts may shift between paginated calls if the directory updates.