CompSuite API
v4
  • v4
  • v3
  • v2
    CompSuite API
    v4
    • v4
    • v3
    • v2
    • API Usage Guidelines
    • Authentication
    • Errors
    • Divisions
      • List all divisions
        GET
    • Groups
      • List all groups
        GET
      • Retrieve a group
        GET
      • Create a Group
        POST
      • Update a group
        POST
    • Seasons
      • List all seasons
        GET
    • Events
      • List all events
        GET
      • Retrieve an event
        GET
      • Create an event
        POST
      • Create a Competition
        POST
    • Performances
      • Add a performance
        POST
      • Delete a performance
        DELETE
    • Schedule
      • Retrieve Schedule for Competition
        GET
    • Scores
      • Retrieve Competition Scores
        GET

    Authentication

    This is an HTTPS-only API and it uses OAuth 2.0 authorization, implementing Authorization Code and Client Credential flows. All requests have to be authenticated via the Authorization header:
    curl -H "Authorization: Bearer f4f4994a875f461ca4d4708b9e027df4" \
        https://api.competitionsuite.com/v3/groups
    Please note that you can choose to send data as JSON or form in all POST requests on this page, as long as the appropriate Content-Type header is included.

    OAuth2 Application Keys#

    You need to create an OAuth2 application before you can use the API. Create one by navigating to your organization > Settings > API and click Create API Key.

    Client Credentials Flow#

    With the Client Credentials flow it is possible to retrieve an access token directly using your application id and application secret:
    curl -X POST https://api.competitionsuite.com/v3/oauth2/token \
        --data "grant_type=client_credentials" \
        --data "client_id={application_id}" \
        --data "client_secret={application_secret}"
    This token is valid for 2 hours and you should create a new one only after the existing token expires. Expiration will be indicated by the API responding with HTTP 401.
    Modified at 2025-07-28 13:21:49
    Previous
    API Usage Guidelines
    Next
    Errors
    Built with