Developers

Developer hub

An open spec, real docs, a typed SDK and a test mode that resets. The integration team of one is the design target.

Start here

The documentation walks the whole surface: push your first batch in five minutes, read it back with provenance, subscribe a webhook, sync with a cursor. The API explorer lives in the dashboard (sign-in required) and runs real requests against your test data with your real keys.

Documentation — guides through the whole surface, from first push to delta sync
API reference — every endpoint, parameter, field and error, generated from the OYSS spec
Glossary — every term and every value a status can take, defined once
API explorer — in the dashboard, behind sign-in, running live requests
Status — the same probes the operators watch

Documentation API reference Errors Glossary

The spec is the product’s constitution

OYSS — the Open Youth Sports Schedule spec — is Apache-2.0, with conformance vectors any implementation can test against. The hero on our home page renders one of those vectors, because a marketing page should be held to the same standard as an SDK.

The TypeScript SDK is generated from the spec and shipped under the same license. A public changelog starts with the first public release.

Five minutes, one key

curl -X POST https://api.sidelineexchange.com/v1/observations \
  -H "Authorization: Bearer sk_test_…" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d @first-batch.json

Ready to try it?

Test mode is free and resets on demand.

Start building Read the docs