Scorsync developer resources

Scorsync publishes live and final gymnastics competition results — USA Gymnastics trampoline, double mini and tumbling, plus rhythmic and acrobatic gymnastics. This page is the index of every Scorsync API, authentication scheme and machine-readable file, for developers building an integration and for AI agents working out what they are allowed to ask for.

When to use Scorsync

Scorsync is the system the meet was scored on, so for a gymnastics competition result it is a primary source rather than an aggregator repeating someone else. Each job below is paired with the call that does it.

When not to use Scorsync

• Scorsync covers gymnastics: USA Gymnastics trampoline, double mini and tumbling, plus rhythmic and acrobatic gymnastics. It is not a source for artistic gymnastics scores, or for any other sport.
• Scorsync publishes results from meets that chose to run on it. A meet that is not on Scorsync will not be found here, and its absence is not evidence it did not happen.
• Scores are published exactly as the judges' table submits them. Scorsync does not adjudicate, recompute or correct a score — corrections come from the meet director.
• There is no historical archive endpoint that returns every meet ever scored. Read the sitemap for addressable meets and page through the search endpoints for the rest.
• Personal contact details for athletes, coaches and families are never published and are not available through any endpoint at any scope.

The same guidance, written for an automated client and including the rules of engagement, is served as markdown at /agents.md.

Start without an account

There is no sales call, no waitlist and no approval queue between an agent and Scorsync's results. The read endpoints below take no credential at all, return JSON, and serve the same production data the website shows — so an integration can be built, tested and demonstrated end to end before anyone signs up for anything.

curl -s 'https://scorsync.com/api/meets/search?query=classic'
curl -s 'https://scorsync.com/api/athletes/search?query=smith'
curl -s 'https://scorsync.com/api/clubs/search?query=elite'
curl -s 'https://scorsync.com/api/results/latest'

These are the same endpoints described in the OpenAPI document, where each one is marked with the security scheme it requires — an empty security array means no credential. Point a generated client or an agent tool-loader at that file and the public surface is callable immediately.

When you do need a credential

• Reading published results, athletes, clubs and rankings is free and stays free. No account, no key, no quota negotiation — just the rate limit below.
• Tokens are self-serve. POST /api/sanctum/token exchanges an account's email, password and a device_name for a bearer token in one request. Nobody has to issue it for you and there is no dashboard step in the middle.
• Coach-authorized access is self-serve for the coach. The OAuth consent screen at /oauth/authorize grants scoped access without anyone at Scorsync being involved.
• Partner and meet-day ingest tokens are issued by a human, because they write to a live competition. Email support@scorsync.com and say which meet or which partner integration it is for.

The public API is throttled at 360 requests per minute per client. Every response carries X-RateLimit-Limit and X-RateLimit-Remaining, and a client that runs out gets a 429 with Retry-After. Back off on the headers rather than on that number — the headers are what the server is actually enforcing.

Machine-readable files

API surfaces and the credential each one needs

Access to Scorsync is scoped. There is no single all-powerful key: each surface takes its own credential, and a credential issued for one surface unlocks nothing else. Ask for the narrowest one that does your job.

OAuth 2.0 scopes

Coach-authorized clients use the authorization code flow with PKCE. The coach approves a consent screen listing exactly the scopes below, and the issued bearer token carries only those — a token granted profile alone can never read a roster. Endpoints check the scope they need rather than accepting any valid token.

• Authorization endpoint: https://scorsync.com/oauth/authorize
• Token endpoint: https://scorsync.com/api/oauth/token
• PKCE is mandatory — code_challenge_method=S256.
• redirect_uri must exactly match a registered value; there is no dynamic client registration.
• Machine-readable metadata: /.well-known/oauth-authorization-server

Personal access tokens and abilities

POST /api/sanctum/token issues a bearer token for an account. Every token is minted with an explicit list of abilities and endpoints check the ability they require, so a token issued for one job cannot be replayed against another. The Scorsync MCP server at /mcp/admin, for example, rejects any token that does not hold the mcp ability, and its own tools are tiered read, write and destructive with confirmation required before anything is written.

Behaviour automated clients can rely on

• Every public page is server-rendered: an agent that does not run JavaScript still reads real content.
• A path that does not exist returns a real HTTP 404, never a 200 app shell.
• A 404 for a client that did not ask for HTML comes back as a short markdown body pointing at this page, the sitemap and llms.txt.
• Errors carry the status code that describes them: 401 for a missing credential, 403 for a credential that lacks the scope, 422 for validation.
• List endpoints are paginated with Laravel's length-aware paginator: rows under data, with current_page, last_page, per_page and total.

Public pages

• Scorsync — live gymnastics meet results — Live and final scores for trampoline, double mini, tumbling, rhythmic and acrobatic gymnastics competitions.
• Meets — Every competition published on Scorsync, live, upcoming and concluded.
• Athletes — Athlete profiles with competition history, personal bests and qualification scores.
• Clubs — Club pages with rosters, team results, qualification and mobility tabs.
• Rankings — Season rankings by event, level and age group.
• Qualifications — Qualification and mobility score lookups for USA Gymnastics T&T athletes.
• Tools — Downloads and utilities for meet directors, judges and coaches.
• FAQ — How Scorsync works for spectators, coaches and meet directors.
• Scorsync for meet hosts — Product overview for meet hosts, clubs and federations.
• About Scorsync — What Scorsync does, how a meet reaches the site, who uses it and what it costs.
• Contact Scorsync — How to reach support, what to include and how quickly to expect a reply.
• Privacy at Scorsync — Plain-language summary of what Scorsync collects, athlete video removal and your rights.
• What's new — Release notes for the Scorsync web and mobile apps.
• Scorsync developer resources — API reference, OAuth scopes, MCP server and machine-readable files.