Operator APIs | Data Ingestion | CSV to API
CSV Samples
The CSV to API connector will accept 4 different file formats. Kindly note that Green headers are required, Blue headers are required but if client does not provide the value the connector will use a default value (according to the logic below), Orange headers are not required.
When using CSV to API, the files will be processed on a first come, first served basis (FIFO). Therefore, it is important to send events to the system in chronological order to ensure proper processing.
Logic for New Definition
Player > Acquisition Event
PlayerDirect > Acquisition Event
Activity > Activity, Deposit, Withdrawal, Correction, Adjustment Event
Exchange Rate Files > Exchange Rate Change Event
Verified Customers Files > Player Status Event
Deposit/Withdrawal Methods
The following is a list of pre-defined deposit and withdrawal methods:
Deposit Method
Withdrawal Method
ID
UN
CHEQUE
CLICK BUY
CREDEB
CREDEB MARKETING
CREDEB POKER
ENVOY
Skrill
NETTELLER
PAYPAL
PAYAL FEE
TRANSFER
UNKNOWN
WEB MONEY
Bank Transfer
Ukash
InstaDebit
Debit/Credit Card
Voucher
Tigo Pesa
Vodacom M-Pesa
PaySafeCard
Rapid Transfer
Postepay
Trustly
Revolut
ClickandBuy
ecoPayz
Entropay
Yandexmoney
Moneta
Sofort
CryptoCurrencies
MUCHBETTER
eZeeWallet
AstroPay
Apple Pay
Google Pay
NetBanking
Paytm
PhonePe
UPI
Boku
Multibanco
Giropay
Qiwi Wallet
SafeCharge
HiPay
CartaSi
Interac
Euteller
MB WAY
Zimpler
PugglePay
Klarna
Neosurf
POLi
Ozow
SiD
Peach Payments
OTT Voucher
zapper
1ForYou
airtel
HalCash
P24
Halopesa
EzyPesa
Selcom Paypoint
iDEAL
Mifinity
Siru Mobile
Bizum
INOVAPAY
Pay4Fun
CashtoCode
Banco Posta
Flexepin
WeChat Pay
Alipay
Jeton
Dash
Bambora
Other
UN
CHEQUE
CLICK BUY
CREDEB
CREDEB MARKETING
CREDEB POKER
ENVOY
Skrill
NETTELLER
PAYPAL
PAYAL FEE
TRANSFER
UNKNOWN
WEB MONEY
Bank Transfer
Ukash
InstaDebit
Debit/Credit Card
Voucher
Tigo Pesa
Vodacom M-Pesa
PaySafeCard
Rapid Transfer
Postepay
Trustly
Revolut
ClickandBuy
ecoPayz
Entropay
Yandexmoney
Moneta
Sofort
CryptoCurrencies
MUCHBETTER
eZeeWallet
AstroPay
Apple Pay
Google Pay
NetBanking
Paytm
PhonePe
UPI
Boku
Multibanco
Giropay
Qiwi Wallet
SafeCharge
HiPay
CartaSi
Interac
Euteller
MB WAY
Zimpler
PugglePay
Klarna
Neosurf
POLi
Ozow
SiD
Peach Payments
OTT Voucher
zapper
1ForYou
airtel
HalCash
P24
Halopesa
EzyPesa
Selcom Paypoint
iDEAL
Mifinity
Siru Mobile
Bizum
INOVAPAY
Pay4Fun
CashtoCode
Banco Posta
Flexepin
WeChat Pay
Alipay
Jeton
Dash
Bambora
Other
0
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
Data Ingestion Data Model and Error Codes
Learn more about common Data Ingestion Developer error codes and how to resolve them.
Error codes describe events’ validation statuses of the DATA INGESTION API.
If you don't find an error code listed here, please refer to the API-specific error codes in their respective documentation pages.
All events are sent in batches but processed individually. If all events are valid, then 200 will be returned. If some of the events are not valid, then 207 will be returned. If all the events are not valid, then 400 will be returned.
Additional validation for all event types:
multiple events with the same EventID must not be processed
JSON with unproper multiple structures must not be processed
