SportsX Partner APISigned server-to-server access

Workspace-isolated, fail-closed authorization and bilingual generated contracts

Signed requests

Every /v1 operation requires the four X-Sx signature headers; Bearer authentication is not accepted.

A verified credential resolves one caller and one club or federation; wrong-kind and foreign resources return 404.

Positive scope provisioning remains unavailable; the isolated Partner worker delivers webhooks, whose consumers must still reconcile canonical state.