Competier
    Competier
    • api-key
      • Creates and returns a new api key, invalidating the previous one.
        POST
    • ladder
      • Adds a ladder to an account.
        POST
      • Deletes a ladder from an account, including all its entries, ratings and results.
        DELETE
      • Gets ladders of an account.
        GET
    • ladder-entry
      • Adds a self-managed entry to a ladder.
        POST
      • Deletes a ladder-entry from a ladder, including all its ratings and results.
        DELETE
      • Gets ladder entries.
        GET
    • result
      • Adds a game result for a played game.
        POST
      • Deletes a game result by rolling it back, reverting rating changes.
        DELETE
      • Gets game results.
        GET
    • invite
      • Adds an invite.
        POST
      • Accepts an invite.
        PUT
      • Deletes an invite.
        DELETE
      • Gets invites.
        GET
    • account
      • Updates account data.
        PATCH
    • credit
      • Fetches credit info.
        GET
    • matchmaking
    • bulk

    bulk

    Developing
    wss://api.competier.net/ws/v1/bulk
    [Not yet functional. Please contact us directly if you need something like this.]
    In some cases, it can be useful to be able to post a lot of results or ladder-entries from a single client. Maybe you're hosting a gameserver where a lot of users are simultaneously participating in fast-paced duels that you want to track and rate, or maybe you're moving an already existing stack of results and entries to Competier. For situations like this, we also offer a websocket interface to get rid of the massive per-request overhead accompanying HTTP.
    After establishing a websocket connection, you can simply send ladder-entries and results in JSON format as messages, which will be treated just like POST HTTP requests. You'll also get similar responses, including HTTP response codes, exactly as if you had used the respective HTTP routes.
    Websocket connections are billed 1 credit per minute started or per 100 messages started, whatever is higher. Therefore, you can process a bulk of data much more cheaply than with the HTTP interfaces. Websocket connections time out after 120 seconds without messages.

    Request

    Header Params
    Authorization
    string 
    optional
    Example:
    Bearer 2f68dbbf-519d-4f01-9636-e2421b68f379
    Previous
    matchmaking
    Built with