Reep Next reads from generated release artefacts, not the private register
database. The customer launch namespace is /api/v1;
/api/next remains the staging namespace.
The interactive reference below is the Reep Next v1 contract
(schema public-bridge-register-v2): the entity envelope with
typed aliases, sourced attributes, provider bridges, the Wikidata overlay,
and grouped relationships. Authenticate with Authorization: Bearer
<key>; the /api/next namespace is identical.
What relationships cover. Published relationships are the structural spine — competition, season, stage and match, plus which teams participate in which competition-seasons. Players, coaches and referees are identity records: they carry provider bridges, names and aliases, and their relationship list is empty by design. Career histories, squad memberships and appearance data are matching evidence held privately, not part of the open bridge register. If you need to map a player across providers, that is exactly what the bridges give you; if you need career structure, it is not published here.
Reep Register