Introduction

The MyMenopauseRx Developer API lets partners build on our care infrastructure for women in menopause. Today it exposes the public provider directory — our Menopause Society Certified clinician roster, complete with credentials, licensed states, accepted insurance, and appointment types.

This is the same data that powers our own "find a provider" experience, served over a clean, predictable JSON API you can read directly from a browser or a backend.

Base URL

https://api.mymenopauserx.com

All endpoints are versioned under /v1. Responses are JSON. The directory is public and read-only — no API key, no BAA, no CORS gymnastics.

What you can build

Conventions

• Identifiers — providers have a stable, opaque id and a human-readable slug. Link by slug; store the id. Each profile also carries a canonical profileUrl you can link to directly.
• Pagination — list responses echo back the limit and offset applied (after clamping) plus a total count across all pages.
• States — two-letter US state codes (CA, NY, …) throughout. Don't hard-code them: /v1/states returns the states we actually serve, each with an appointmentTypeCount so you can skip the empty ones. A profile's statesLicensed and statesAcceptingPatients are separate lists: the state filter matches licensure, so check statesAcceptingPatients when you need to know who's actually taking new patients.
• Filtering — you can filter the list by state, insurance, providerType (a camelCase enum: physician, nursePractitioner), and gender. The accepted insurance values come from /v1/insurances (optionally scoped to a state), so you can populate a filter rather than guessing. menopauseSocietyCertified is returned on every profile but is not a filter — read it per-provider rather than querying for it.
• Nullability — optional fields such as gender and headshotUrl are nullable; handle a null (or absent) value rather than assuming the field is always populated.