This operation is used to assign players to upcoming or running campaigns. The specified player will be created, if not exists already.
Request
PARAMETER | DESCRIPTION | FORMAT | EXAMPLE |
partnerID | ID of partner Unique ID associated with each customer |
GUID | D61A14AE-0A0C-464B-B7AB-5900BE7462F9 |
sign | Parameters partnerID, players, campaignCode, currency (for more information, see Creating Data Sign) |
string (64) | 5E0A0349AE36AD67 CD21D891AB124CCE 8CC4171C5BD7EF5B 26FCA86DB71F500A |
players | Names of players separated by semicolon | string | Player01;Player02 |
campaignCode | Code of the campaign | string (32) | Customer_1 |
currency | Currency of the player. This value is in ISO 4217 format, so it is expressed with 3 letters. | string (3) | USD |
Request example:
REST JSON
POST https://staging.tomhorngames.com/services/gms/RestCustomerIntegrationService.svc/AssignPlayerToCampaign HTTP/1.1
Accept-Encoding: gzip,deflate
Content-Type: application/json
Content-Length: 123456
Host: staging.tomhorngames.com
{
"partnerID" : "9a2e7402-5cef-42ed-84a6-db589ce19fc6",
"sign" : "E8C1A3EB1BDD263B9FB5213AFFF8AEF909F0D9934BFFEDAD481091CDE36EB365",
"players" : "Player01;Player02",
"campaignCode" : "Customer_1",
"currency" : "EUR"
}
Response
PARAMETER | DESCRIPTION | FORMAT | EXAMPLE |
Code | Result codes: 0, 1, 11, 1001, 1002, 1034, 1035, 1036 (for more information, see Result Codes) | integer | 0 |
Message | Description of the error, if one has occurred. This value is filled only in the event that an error takes place. | string (256) | Cannot find specified identity |
Response example:
REST JSON
{
"Code": 0,
"Message": null
}
SOAP
<AssignPlayerToCampaignResult> <Code>0</Code> <Message></Message> </AssignPlayerToCampaignResult>
Comments
0 comments
Article is closed for comments.