WEBHOOK
authentication-endpoint
{
  "authMethod": "facebook",
  "token": "<string>",
  "date": "2023-11-07T05:31:56Z",
  "appID": "<string>",
  "userName": "<string>",
  "password": "<string>",
  "os": "ios",
  "utmSource": "<string>",
  "utmMedium": "<string>",
  "utmCampaign": "<string>"
}
{
  "status": "<string>",
  "playerProfileImage": "<string>",
  "publisherPlayerId": "<string>",
  "playerName": "<string>",
  "sessionMetadata": {}
}

POST HTTP request to the game server with an URL configured in the dashboard.

Notes: You can read more about how Appcharge handles Player Authentication, and the Player Authentication Webhook, in the Guides section. It’s important to ensure that the schema on the receiving end is flexible rather than rigid. This will allow the publisher to receive any extra properties we may introduce in the future without causing issues or requiring changes on their end.

Headers

​
x-publisher-token
string
required

The publisher token.

​
signature
string
required

The signed payload.

Body

application/json

Response

200
application/json

Login successful.

The response is of type object.