Brown Bears APIbrownbears.com ↗
Retrieve the full Brown University men's lacrosse roster via API. Returns player names, positions, jersey numbers, class years, and hometowns in one request.
What is the Brown Bears API?
The Brown Bears Lacrosse Roster API exposes 1 endpoint — get_roster — that returns the complete current men's lacrosse roster for Brown University Athletics. Each response includes 6 fields per player: full name, position, jersey number, class year, hometown, and home state. The entire roster is returned in a single call, ordered by jersey number, with a total player count included at the top level.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/3b3aec82-ca52-47f5-b5ca-cc7818e8317a/get_roster' \ -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 brownbears-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: Brown Bears Men's Lacrosse Roster — list all players."""
from parse_apis.brownbears_com_api import BrownBears, ParseError
client = BrownBears()
# Fetch the full roster, capped at 60 players
try:
for player in client.players.list(limit=60):
print(f"#{player.jersey_number} {player.name} — {player.position}, {player.class_year} ({player.hometown}, {player.home_state})")
except ParseError as e:
# Roster page may change structure between seasons
print(f"Extraction failed: {e}")
print("exercised: players.list")
Returns the full current men's lacrosse roster for Brown University. Each player entry includes full name, position, class year (Fr./So./Jr./Sr./Gr.), jersey number, hometown, and home state. The roster is returned in jersey number order. One request fetches all players; no pagination needed.
No input parameters required.
{
"type": "object",
"fields": {
"total": "integer count of players on the roster",
"players": "array of player objects with name, position, class_year, jersey_number, hometown, and home_state"
},
"sample": {
"data": {
"total": 51,
"players": [
{
"name": "Nicholas Snyder",
"hometown": "Boca Raton",
"position": "D",
"class_year": "So.",
"home_state": "Fla.",
"jersey_number": "1"
},
{
"name": "Jayden Vega",
"hometown": "Port St. Lucie",
"position": "A/M",
"class_year": "So.",
"home_state": "Fla.",
"jersey_number": "2"
},
{
"name": "Brady O'Kane",
"hometown": "West Chester",
"position": "A",
"class_year": "Jr.",
"home_state": "Pa.",
"jersey_number": "3"
}
]
},
"status": "success"
}
}About the Brown Bears API
What the API Returns
The get_roster endpoint returns the full active roster for Brown University's men's lacrosse program, sourced from the official Brown Bears Athletics site at brownbears.com. The top-level response contains a total integer indicating how many players are on the roster, alongside a players array where each object carries name, position, class_year, jersey_number, hometown, and home_state.
Player Fields in Detail
Class year values follow standard NCAA abbreviations: Fr., So., Jr., Sr., and Gr. (graduate). Jersey numbers are returned as the ordering key for the array, so the first element in players corresponds to the lowest jersey number on the team. Hometown and home state are separate fields, making it straightforward to filter or group players by geography without string parsing.
Scope and Freshness
The endpoint covers only the current season's active roster as published on brownbears.com. There are no input parameters — one request fetches all players with no pagination. The data reflects the official Athletics roster page, so any mid-season roster changes (additions, departures) will surface as those updates appear on the source page.
The Brown Bears API is a managed, monitored endpoint for brownbears.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when brownbears.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 brownbears.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 team directory widget for a Brown lacrosse fan site, displaying player name, position, and jersey number.
- Analyze recruiting geography by grouping players by
home_stateto map where Brown sources its lacrosse talent. - Track class-year distribution across the roster to understand how many freshmen, juniors, or graduate players are active.
- Populate a fantasy or pick'em app with current Brown lacrosse player data for Ivy League sports competitions.
- Generate automated program summaries that include current roster size via the
totalfield alongside positional breakdowns. - Monitor roster changes over time by polling the endpoint periodically and comparing player arrays across snapshots.
| 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 Brown University Athletics offer an official developer API?+
What does `get_roster` return for each player, and can I filter by position?+
name, position, class_year, jersey_number, hometown, and home_state. The endpoint returns all players in one response with no server-side filtering — you apply any position or class-year filtering client-side after receiving the full players array.Does the API cover historical rosters or stats beyond the current season?+
Does the API include women's lacrosse or other Brown Athletics programs?+
How current is the roster data, and how often does it update?+
players array is the recommended approach.