BETCORE Aggregator
Provider IntegrationCasino Integration
Provider IntegrationCasino Integration
Visit Betcore website
Follow Betcore on Instagram
Follow Betcore on LinkedIn
Follow Betcore on Youtube
  1. Authorization
  • 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
        • Make
        • Make-list
        • Close
      • 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
          POST
      • Games
        • Info
        • Translations
      • Jackpot
        • Accumulated
    • Websocket
      • SubOnWholeGamesInfo
  • SubOnWholeGamesInfo
  1. Authorization

Token

POST
/backend.bcdprod.net/partnersmediator-service/api/v2/auth/token

Overview#

The Token endpoint is used to securely authenticate the Partner within the BETCORE system and obtain an access token. This token grants access to protected resources and functionalities, enabling integration with BETCORE services.The main objectives of this method are:
Authentication: To verify the identity of the Partner using the PartnerClientId and Secret.
Authorization: To determine the specific permissions granted to the Partner, as defined by the scope of the access token.
Access Token Issuance: To provide the Partner with a valid access token for subsequent requests to protected resources.

Request

Body Params application/json
PartnerClientId
number 
required
Partner's client ID.
Secret
string 
required
Secret key.
Example
{
    "PartnerClientId": 1556,
    "Secret": "17aec...2521"
}

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/backend.bcdprod.net/partnersmediator-service/api/v2/auth/token' \
--header 'Content-Type: application/json' \
--data-raw '{
    "PartnerClientId": 1556,
    "Secret": "17aec...2521"
}'

Responses

🟢200Success
application/json
Body
Value
object 
required
id_token
string 
optional
Identification token.
access_token
string 
required
Access token.
expires_in
number 
required
Token lifetime in seconds.
token_type
string 
required
Token type.
refresh_token
string 
optional
Refresh token.
scope
string 
required
Specifies the APIs that a JWT is authorized to access.
ErrorCode
number 
required
Error code of the response.
Message
string 
required
Code description.
Example
{
    "ErrorCode": 200,
    "Message": "Success",
    "Value": {
        "id_token": null,
        "access_token": "eyJhbGciOiT8a...Hk8-R-HiLVpumYMo",
        "expires_in": 900,
        "token_type": "Bearer",
        "refresh_token": null,
        "scope": "external-client-api feeds-api signalr-feed-api"
    }
}
⚪103752Invalid request parameters
Previous
REST API
Next
Info
Built with