ffvbbeach APIffvbbeach.org ↗
Access FFvolley competition data: pool standings, match calendars, weekly schedules, club directories, and official match sheets via 10 structured endpoints.
What is the ffvbbeach API?
The ffvbbeach.org API covers French volleyball competition data across all levels — national, regional, and departmental — through 10 endpoints. Starting with list_organizations, you can enumerate roughly 100 organizing bodies and then drill into pool standings, match calendars, weekly programmes, club schedules, contact directories, and official electronic match sheets (FDME), all returning structured JSON with no pagination required on most endpoints.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/f064dafa-0ce9-4335-a9b3-fa2d152c0cbb/list_organizations' \ -H 'X-API-Key: $PARSE_API_KEY'
Lists every competition-organizing body whose results are published: national competition groups (seniors, youth, masters, beach, para-volley, Compet'Lib), regional leagues, and departmental committees. One round trip; returns the full list (around 100 entries) with no pagination. The organization_code is the key accepted by list_pools, get_pool and get_weekly_schedule. level is derived from the code prefix (national / league / departmental).
No input parameters required.
{
"type": "object",
"fields": {
"count": "number of organizations returned",
"organizations": "array of organizing bodies: organization_code (string key), name (French label), level (national | league | departmental)"
},
"sample": {
"data": {
"count": 100,
"organizations": [
{
"name": "Compétitions Nationales SENIORS",
"level": "national",
"organization_code": "ABCCS"
},
{
"name": "Ligue PAYS DE LA LOIRE",
"level": "league",
"organization_code": "LIPL"
},
{
"name": "CD44 - Comité de Loire-Atlantique",
"level": "departmental",
"organization_code": "PTPL44"
}
]
},
"status": "success"
}
}About the ffvbbeach API
What the API Covers
The API exposes competition data published by the French Volleyball Federation (FFvolley) and its affiliated regional leagues and departmental committees. list_organizations returns every organizing body — national groups for seniors, youth, masters, beach, para-volley, and Compet'Lib, plus all regional and departmental bodies — identified by an organization_code string that flows into every other endpoint. list_pools then enumerates the pools (poules) an organization runs in a given season, returning pool_code, pool_name, and the competition heading each pool sits under.
Pool Standings and Match Calendars
get_pool is the core data endpoint: given an organization_code and pool_code, it returns the full standings table and the match calendar in one call. Standings rows include rank, team, points, played, won, lost, forfeits, all six scoreline buckets (w_3_0 through l_0_3), sets won and lost, rally points for and against, and set and point ratios. The match calendar is grouped into rounds (e.g. Journée 01), each with match objects carrying match_code, ISO date, kick-off time, home and away team names, and the score when played. The full_calendar boolean parameter controls whether you receive every round of the season or only the site's recent-and-upcoming window.
Schedules and Directories
get_weekly_schedule returns all matches an organizing body has scheduled in the week containing a given ISO date, sortable by pool (sort=match) or by day (sort=date), with week_start and week_end boundaries in the response. get_club_schedule and get_club_standings take a 7-digit club_id and return, respectively, the club's week programme across every competition level it participates in and the standings of every pool that club has a team in. get_club_directory returns the team address book for an organization: one row per engaged team with the club's president, coach, assistant coach, correspondent address, phone, mobile, e-mail, and playing venues (name, address, capacity).
Match Sheets and Full-Season Exports
get_match_sheet fetches the official FDME document for a single match identified by match_code and organization_code. The response includes both rosters with shirt numbers, names, and licence numbers; liberos; bench staff; set-by-set scores with points, timeouts, and substitutions; and match totals. get_organization_calendar exports the complete season calendar of an entire organizing body in one call — every pool, every match — which can run to several thousand matches for a regional league. Both accept the optional season parameter in YYYY/YYYY+1 form; when omitted, the current season is derived automatically.
The ffvbbeach API is a managed, monitored endpoint for ffvbbeach.org — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when ffvbbeach.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 ffvbbeach.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?+
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 live standings tracker for national Elite Féminine or Nationale Masculine pools using
get_poolstandings rows. - Power a club-facing dashboard showing weekly fixtures and results across all competition levels via
get_club_schedule. - Aggregate full-season match data for a regional league in one call with
get_organization_calendarto feed statistical analysis. - Display official match sheet rosters and set-by-set scores for post-match reporting using
get_match_sheet. - Create an organization directory listing every league and departmental committee with contact details from
get_organization_contacts. - Populate a venue and club contact database from the address book returned by
get_club_directory. - Generate weekly competition programmes grouped by day or pool using
get_weekly_schedulewith thesortparameter.
| 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 ffvbbeach.org provide an official public developer API?+
What does `get_match_sheet` return, and is it available for all matches?+
get_match_sheet returns the official FDME electronic match sheet: header fields (pool, round, date, time, city, hall, category), both team rosters with shirt numbers, names, and licence numbers, liberos, bench staff, and set-by-set detail including points, timeouts, and substitutions per set plus match totals. The sheet is only populated when the match has been played and the FDME has been submitted; for unplayed matches played will be false and set results will be absent.Does `list_pools` include knockout cup draws?+
list_pools. The endpoint covers league-format pools identifiable by a pool_code. You can fork this API on Parse and revise it to add an endpoint covering cup bracket data if that format becomes available.Is beach volleyball competition data available, or only indoor volleyball?+
list_organizations under the national level and flow through list_pools and get_pool like any other competition. However, individual player statistics within matches are not currently exposed by any endpoint. You can fork this API on Parse and revise it to add a player-stats endpoint if that data is accessible.How large can `get_organization_calendar` responses be, and are there performance implications?+
get_pool with full_calendar=true or get_weekly_schedule will return data faster by scoping to one pool or one week respectively.