Delivery headers
- X-Sporthouse-Event
- Event type
- X-Sporthouse-Delivery
- Stable delivery ID
- X-Sporthouse-Timestamp
- Unix timestamp
- X-Sporthouse-Signature
- v1 HMAC-SHA256
Sporthouse Developers
Developer console
Connect programs, teams, rosters, and schedules through an organization-approved API designed around explicit permissions and tenant safety.
Sporthouse signs the exact request body and retries transient failures. Treat the delivery ID as the idempotency key and reject timestamps older than five minutes.
program.updatedregistration.createdroster.updatedteam.updatedschedule.updatedpayment.status_changedPayloads contain organization-scoped identifiers and the specific change, not unrestricted records.
import hashlib, hmac
key = hashlib.sha256(webhook_secret.encode()).digest()
signed = f"{timestamp}.".encode() + raw_request_body
expected = hmac.new(key, signed, hashlib.sha256).hexdigest()
hmac.compare_digest(f"v1={expected}", signature_header)Private applications can connect to the organization that created them. Public Marketplace publishing remains review-gated while the ecosystem is established.
Create a private application in the Developer Console and save the one-time client secret.
Send an administrator through Authorization Code with PKCE S256 to approve only the access you need.
Use a short-lived Bearer token against the versioned API and rotate refresh tokens on every exchange.
The first surface is intentionally small and allowlisted. Every request is pinned to the authorizing organization.
/api/v1/programsProgram identity, dates, sport, status, location, and capacity.
programs:read/api/v1/teamsTeams associated with programs owned by the authorized organization.
teams:read/api/v1/rostersRegistration, participant, program, team, and roster status identifiers.
rosters:read/api/v1/schedulesOrganization events, times, locations, teams, and operational status.
schedules:readcurl https://api.sporthouse.ai/api/v1/programs \
-H "Authorization: Bearer $SPORTHOUSE_ACCESS_TOKEN"Sporthouse apps are designed to fail closed. Credentials are never stored in plaintext, access can be revoked immediately, and every API request creates an audit record.
Consent, PKCE, scoped tokens, tenant isolation, rate limits, and audits.
Retryable, idempotent event delivery with testing and failure visibility.
The first add-on built against the same contract available to partners.
Certification, listings, versioning, billing, and operational controls.