Update player

IMPORTANT

The update player endpoint is a QUEUE & TIME & USER sensitive/locked endpoint at a set time of 30 minutes what this means is it can only be used every 30 minutes on 1 specific player.

Know the do's and don'ts

Understanding how to use this endpoint is important, not only for you and your users but for our systems and others using it.
When an update request is made for a user there are a few things that happen:

The queried user is placed in queue

When its that players turn in queue their data is then updated

This process can take up to 30 minutes for the players data to update. In most cases though its done within 0 - 5 minutes

when an update request is made a lock is put in place to prevent any future update requests for the queried player for 30 minutes.

Like you our system has flaws and in special cases users have been able to get themselves stuck in a data loop. This happens because each time an update request is made for the queried user their place in the queue starts over which results in a longer wait for their data to update if it updates at all. most cases waiting a 30 minute cycle fixes this loop but if it doesn't then the result is you having to contact support to get the user out of the data loop.

Request

Path Params

query

string

required

The unique identifier of the player (could be a username or uid) for which the data is updated.

Example:

player123

Header Params

x-api-key

string

required

The API key for authorization. It is necessary to provide a valid API key to access the data.

Example:

your-api-key-here

application/json

Successful response indicating that the player data was updated.

Body

success

boolean

required

Indicates whether the update was successful.

message

string

required

IMPORTANT#

Know the do's and don'ts#

Request

Responses

IMPORTANT

Know the do's and don'ts