BETCORE Aggregator
Provider IntegrationCasino Integration
Provider IntegrationCasino Integration
Visit Betcore website
Follow Betcore on Instagram
Follow Betcore on LinkedIn
Follow Betcore on Youtube
  1. Payments
  • Getting Started
  • Integrate BETCORE Games (Casino)
    • Integrate BETCORE Gems (Casino)
    • WebFrame Connection
    • Aggregator API for Casino
      • Authentication
        • Verify
        • Jwks
        • Token
      • Payments
        • Accept
      • Cashback
        • Accept
    • Casino API for Aggregator
      • Users
        • Auth
        • Data
      • Payments
        • Info
          POST
        • Make
          POST
        • Make-list
          POST
        • Close
          POST
      • Cashback
        • Make
  • Integrate as Games Provider
    • Integrate as Games Provider
    • Provider API for Aggregator
      • Games
        • Games
        • Launch
    • Aggregator API for Provider
      • Get Balance
        • Balance
      • Bets
        • PayIn
        • PayOut
        • PayInOut
        • Refund
  • Feed
    • Feed Integration
    • REST API
      • Authorization
        • Token
      • Games
        • Info
        • Translations
      • Jackpot
        • Accumulated
    • Websocket
      • SubOnWholeGamesInfo
  • SubOnWholeGamesInfo
  1. Payments

Make-list

POST
/payments/make-list

Overview

The Make-list endpoint is designed for submitting a batch of transactions in a single request. This method enables to efficiently process and send multiple bet-related transactions together rather than one-by-one.

The main objectives of the Make-list method are:

  • Batch Processing of Transactions: The primary objective of this method is to allow aggregation of multiple transactions (such as bet placements, payouts, bet returns, or jackpot transactions) into a single request. This is particularly useful when transactions can be grouped based on criteria like the Partner's user identifier, game type, or client identifier.
  • Efficient Data Transfer: By sending a list of transactions in one go, this endpoint helps reduce the number of individual API calls, thereby improving network efficiency and reducing processing overhead on both the Partner and BETCORE systems.

In summary, the Make-list method facilitates the collective transmission of multiple transactions in a single API call, enhancing processing efficiency, reducing overhead, and ensuring consistent handling and reconciliation of grouped transaction data within the BETCORE system.

Request Parameters

Parameter Data type Description Required
JWT payload
data json string Request data. Yes
  BetId number Bet ID. Yes
  PartnerUserId string Partner's user ID. Yes
  TransactionType number Transaction type:
-1 - accept bet
1 - payout (amount 0 means loss)
2 - bet return
-2 - payout return
4 - jackpot payout
Yes
  Amount string Amount in player's currency. Yes
  TaxAmount string Tax Amount.
The TaxAmount field will be included in the request if the "Tax On/Off" setting is enabled in the BETCORE Backoffice.
No
  PromoCode string Promo code. No
  TagId number Identification tag for an embedded iFrame page element; relevant for Partners using WebFrame as a client.
See more on Tags.
No

Request

Authorization
Add the parameter
Authorization
to Headers
Example:
Authorization: ********************

Request samples

Shell
JavaScript
Java
Swift
Go
PHP
Python
HTTP
C
C#
Objective-C
Ruby
OCaml
Dart
R
Request Request Example
Shell
JavaScript
Java
Swift
curl --location --request POST 'https://mock.apidog.com/m1/820627-0-default/payments/make-list'

Responses

🟢200Success
application/json
Body
ErrorCode
number 
required
Error code of the response.
Message
string 
required
Code description.
Example
{
    "ErrorCode": 200,
    "Message": "Success"
}
⚪103752Invalid request parameters
⚪103811JWT token validation failed
⚪103805Invalid token
⚪103799General API Error
Previous
Make
Next
Close
Built with