Discover/USREPS API
live

USREPS APIusreps.org

Query the US Registry of Exercise Professionals for certified trainers, credential codes, expiration dates, and locations via a single search endpoint.

Endpoints
1
Updated
2h ago

What is the USREPS API?

The USREPS API gives programmatic access to the US Registry of Exercise Professionals public directory through 1 endpoint, search_professionals, which returns up to 500 credential records per broad query. Each result includes the professional's name, certifying organization code, specific credential code, expiration date, location, job role, and whether the credential carries portable (endorsed) status. All filter parameters are optional and combinable.

This call costs1 credit / call— charged only on success
Try it
City name.
1-based results page; 12 rows per page.
Two-letter US state or territory code.
Job role filter from the registry's Job Role dropdown.
Filter on whether the credential is portable (endorsed). Omitted = no filter.
Last name (substring match).
Specific credential code (organization-credential) to filter on.
First name (substring match).
Postal code, leading zeros preserved.
Certifying organization code from the registry's Organization Name dropdown.
Radius in miles around postal_code; requires postal_code.
Exact credential/certification number as issued by the organization (e.g. one shape: T160093).
api.parse.bot/scraper/9b24e329-9557-4d23-9b5e-3259d530336a/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/9b24e329-9557-4d23-9b5e-3259d530336a/search_professionals?job_role=Personal+Trainer&last_name=Smith' \
  -H 'X-API-Key: $PARSE_API_KEY'
All endpoints · 1 totalmissing one? ·

Searches the USREPS public registry for certified exercise professionals. Every input is optional and all supplied filters are combined (AND); at least one filter should be given, and a search that is too broad is capped by the registry at 500 records (total reports at most 500). Each result row is one credential held by one person, so a person with two credentials appears twice with different credential_number values. Results come 12 per page in the registry's own order (alphabetical by last name); pass page to fetch later pages (omitted = page 1), and has_more tells whether another page exists. Name matching is a substring match on the registry side (e.g. last_name 'Smith' also returns 'Goldsmith'). Dates are returned as the registry prints them, MM/DD/YYYY. search_radius only applies together with postal_code. An empty results array with total 0 means the registry has no matching records. Unrecognized job_role, organization, credential, state or search_radius values are rejected before any request.

Input
ParamTypeDescription
citystringCity name.
pageinteger1-based results page; 12 rows per page.
statestringTwo-letter US state or territory code.
job_rolestringJob role filter from the registry's Job Role dropdown.
portablebooleanFilter on whether the credential is portable (endorsed). Omitted = no filter.
last_namestringLast name (substring match).
credentialstringSpecific credential code (organization-credential) to filter on.
first_namestringFirst name (substring match).
postal_codestringPostal code, leading zeros preserved.
organizationstringCertifying organization code from the registry's Organization Name dropdown.
search_radiusstringRadius in miles around postal_code; requires postal_code.
credential_numberstringExact credential/certification number as issued by the organization (e.g. one shape: T160093).
Response
{
  "type": "object",
  "fields": {
    "page": "integer page returned",
    "total": "integer total matching rows reported by the registry (capped at 500 for broad searches)",
    "results": "array of credential rows: name ('Last, First' as shown), last_name, first_name, organization (certifying body code), credential (credential type code), credential_number, portable ('Yes'/'No'), expiration_date (MM/DD/YYYY), city, state, country, postal_code",
    "has_more": "boolean, true when a further page exists",
    "page_size": "integer rows per page (12)"
  },
  "sample": {
    "data": {
      "page": 1,
      "total": 2,
      "results": [
        {
          "city": "Lincoln",
          "name": "Smith, John",
          "state": "AL",
          "country": "US",
          "portable": "Yes",
          "last_name": "Smith",
          "credential": "CSCS",
          "first_name": "John",
          "postal_code": "35096",
          "organization": "NSCA",
          "expiration_date": "12/31/2026",
          "credential_number": "7248321982"
        }
      ],
      "has_more": false,
      "page_size": 12
    },
    "status": "success"
  }
}

About the USREPS API

What the API Returns

The search_professionals endpoint queries the USREPS public registry and returns an array of credential rows. Each row includes name (formatted as 'Last, First'), last_name, first_name, organization (the certifying body code), credential (the specific credential code), expiration_date, city, state, job_role, and portable (a boolean indicating whether the credential is endorsed as portable across organizations).

Filtering and Pagination

Filters can be combined freely: supply first_name and state together to narrow results to professionals in a specific state, or pair credential with city to locate holders of a particular certification locally. The portable boolean filter, when set, restricts results to endorsed or non-endorsed credentials specifically. Results are paginated at 12 rows per page; use the page parameter (1-based) alongside the total and has_more response fields to walk through multi-page result sets.

Coverage Limits

The registry caps broad searches at 500 total reported records. When total returns 500 and has_more is true after page 42, the query is likely hitting that ceiling and should be narrowed with additional filters such as state, city, or credential. The registry only covers professionals who have voluntarily listed their credentials with USREPS-recognized certifying organizations; it is not an exhaustive directory of all fitness professionals in the US.

Reliability & maintenance

The USREPS API is a managed, monitored endpoint for usreps.org — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when usreps.org 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 usreps.org 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?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • Verify that a personal trainer holds a current, non-expired credential before booking sessions.
  • Build a directory of USREPS-listed fitness professionals filtered by state and city for a gym locator tool.
  • Cross-check job applicants' claimed certifications against the live registry using last_name and credential code.
  • Aggregate credential distribution data by organization and job_role to analyze fitness industry certification trends.
  • Filter for portable (endorsed) credentials to identify professionals whose certifications are recognized across multiple organizations.
  • Automate periodic expiration-date checks for a roster of employed fitness staff to flag upcoming renewals.
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo2005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 req/min
Team$300/mo20,000300 req/min
Company$1,000/mo100,000500 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.

Frequently asked questions
Does USREPS offer an official developer API?+
No. USREPS does not publish a public developer API or documented data feed at usreps.org. This Parse API provides structured access to the public registry data.
What does each result row in search_professionals actually include?+
Each row returns the professional's full name (as 'Last, First'), split last_name and first_name fields, the certifying organization code, the specific credential code, expiration_date, city, state, job_role, and a portable boolean indicating whether the credential is endorsed as transferable.
Why does total stop at 500 even when more professionals likely match?+
The USREPS registry itself caps broad result sets at 500 records. If your query returns total=500 and has_more remains true at page 42, you have hit that ceiling. Add filters such as state, city, credential, or job_role to bring the result set below the cap and retrieve a complete picture of the matching subset.
Does the API expose contact details such as email addresses or phone numbers for listed professionals?+
No. The fields returned are limited to name, location (city/state), credential code, certifying organization, job role, expiration date, and portable status. Contact details are not part of the USREPS public registry data. You can fork this API on Parse and revise it to add any supplemental endpoint if a future registry version exposes contact fields.
Can I look up a professional's full certification history or past credentials?+
Not currently. The API returns the current credential records as listed in the public registry; historical or expired credential records beyond what USREPS currently publishes are not available. You can fork the API on Parse and revise it to add an endpoint targeting any historical data surface USREPS may add in the future.
Page content last updated . Spec covers 1 endpoint from usreps.org.
Related APIs in HealthcareSee all →
ehlers-danlos.com API
Access the Ehlers-Danlos Society's healthcare professionals directory and support group listings. Search and filter providers by location, specialty, profession, and language, and retrieve full provider profiles including contact details and credentials.
nationalpilatescertificationprogram.org API
Access data from nationalpilatescertificationprogram.org.
healthgrades.com API
Search for doctors and healthcare professionals by name and location to find detailed provider profiles including credentials, specialties, and patient reviews. Get comprehensive information about individual practitioners to help you make informed decisions about your healthcare providers.
acefitness.org API
Search through thousands of exercises and fitness articles while getting personalized BMI calculations and locating certified trainers in your area by ZIP code. This comprehensive fitness resource helps you build workouts, learn proper techniques, and connect with professional guidance all in one place.
app.yogaalliance.org API
Access data from app.yogaalliance.org.
biggerpocket.com API
Search and connect with vetted real estate professionals from the BiggerPockets network, including agents, lenders, contractors, and property managers in your area. Find the right service providers for your investment needs by browsing detailed business profiles and contact information.
service.asic.gov.au API
Search and retrieve comprehensive information about Australian financial professionals and entities, including AFS and credit licensees, their representatives, liquidators, auditors, and managed investment schemes. Verify credentials, check regulatory status, and access detailed profiles of financial service providers registered with ASIC.
npidb.org API
Search for healthcare providers and organizations by name to instantly retrieve their credentials, contact information, and specialty taxonomy codes from the National Provider Identifier database. Look up detailed provider profiles to verify qualifications and find the right medical professionals for your needs.