Bryant Bulldogs APIbryantbulldogs.com ↗
Access the current Bryant University men's lacrosse roster via API. Returns player names, jersey numbers, positions, class years, and hometowns in one call.
What is the Bryant Bulldogs API?
The Bryant Bulldogs Men's Lacrosse Roster API exposes 1 endpoint — get_roster — that returns the full current roster with 5 data fields per player: name, jersey number, position, class year, and hometown. The response also includes team name, sport, season year, and a total player count, making it straightforward to build a roster display or sync athlete data without manual updates.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/c8448fcd-0b3b-4ef7-bae6-28eb373b5613/get_roster' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns the current Bryant University men's lacrosse roster. Each player record includes full name, position, class year, jersey number, and hometown/state. The endpoint fetches and parses the live roster page; no pagination is needed as the full roster is returned in one call.
No input parameters required.
{
"type": "object",
"fields": {
"team": "string — team name ('Bryant Bulldogs')",
"sport": "string — sport name ('Men's Lacrosse')",
"season": "string — the roster season year (e.g. '2027')",
"players": "array of player objects with name, jersey_number, position, class_year, hometown",
"total_players": "integer — number of players on the roster"
},
"sample": {
"data": {
"team": "Bryant Bulldogs",
"sport": "Men's Lacrosse",
"season": "2027",
"players": [
{
"name": "Patrick Walsh",
"hometown": "Shelburne, Vt.",
"position": "Attack/Midfield",
"class_year": "Sr.",
"jersey_number": "1"
},
{
"name": "Jordan Hernando",
"hometown": "Mountain Lakes, NJ",
"position": "Faceoff",
"class_year": "Jr.",
"jersey_number": "2"
},
{
"name": "Will Siegenthaler",
"hometown": "Elmhurst, Ill.",
"position": "Attack/Midfield",
"class_year": "Gr.",
"jersey_number": "3"
}
],
"total_players": 50
},
"status": "success"
}
}About the Bryant Bulldogs API
What the API Returns
The get_roster endpoint returns the complete Bryant University men's lacrosse roster as a single response. Each player object in the players array includes name, jersey_number, position, class_year, and hometown. The top-level response also carries team (always 'Bryant Bulldogs'), sport (always 'Men's Lacrosse'), season (e.g. '2027'), and total_players as a convenience count.
Endpoint Behavior and Inputs
get_roster takes no input parameters. The full roster is returned in a single call with no pagination required. Because it reflects the live roster page, the data changes when the athletics department updates the roster — for example when players are added, transferred, or graduate between seasons.
Coverage and Scope
This API is scoped specifically to the Bryant University men's lacrosse program. It does not cover other sports at Bryant, roster histories from prior seasons, or individual player statistics such as goals, assists, or saves. The class_year field identifies each player's academic standing (e.g. freshman, senior), and hometown typically includes both city and state.
The Bryant Bulldogs API is a managed, monitored endpoint for bryantbulldogs.com — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when bryantbulldogs.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 bryantbulldogs.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 roster display widget for a fan site using player names, jersey numbers, and positions
- Track roster changes between seasons by comparing
total_playersand player names across calls - Filter players by
class_yearto identify how many seniors are on the current squad - Map player
hometowndata to visualize the geographic recruiting reach of the program - Sync an athletics database or CMS with the current roster without manual data entry
- Generate depth-chart views organized by
positionfor lacrosse analytics or coaching tools
| 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 Bryant University have an official developer API for its athletics data?+
What exactly does the get_roster endpoint return for each player?+
name (full name), jersey_number, position, class_year (academic year such as freshman or senior), and hometown (city and state). The response wrapper adds team, sport, season, and total_players.