LogoLogo
FeedsIntelligenceEngagementsHelpHome
TRADE360 Integration
TRADE360 Integration
  • Integration Guide
  • RMQ connection
    • Connection and Consumption setup
    • Message Deserializing
    • Market/Bet Message Handling
    • How do I work with TRADE360 feed?
  • Message Structure
    • Message Types Overview
    • Message
    • Events
    • Fixture
    • Competition
    • Markets
    • Bets
    • Participant
    • Livescore
    • Settlements
    • Heartbeat
    • Keep Alive
    • Extra Data
    • Outright Fixture
    • Outright Fixture Market
    • Outright League Fixture
    • Outright League Market
    • Outright Settlements
    • Outright League Settlement
    • Example Messages
    • ProviderMarkets
  • APIs
    • Metadata
    • Subscription
    • Distribution
    • Snapshot
    • Notes and Troubleshooting
  • Enumerations
    • Fixture/Scoreboard Status
    • Subscription
    • Message Types
    • Bet Suspension Reasons
    • Fixture Extra Data
    • Status Description
    • Statistics and Incidents
    • Periods
    • Bet Settlements and Statuses
    • Livescore Extra Data
    • Languages
  • SDK
    • SDK Overview
    • Configuration
    • SDK Installation Guide NodeJS
    • SDK Installation Guide .NET
    • SDK Installation Guide Java
  • Code Samples
    • RMQ Consumer (PHP)
    • RMQ Consumer (GO)
    • RMQ Consumer (Node.js)
    • RMQ Consumer (Python)
    • RMQ Consumer (JavaScript)
    • RMQ Consumer (C#)
Powered by GitBook
On this page

Was this helpful?

  1. APIs

Distribution

PreviousSubscriptionNextSnapshot

Last updated 1 month ago

Was this helpful?

This documentation outlines a set of API endpoints for managing and interacting with TRADE360's Queue, including distribution management and status.

Starting from 25/09/24, the consumers property will no longer include the consumer's name and IP. Instead, it will provide the number of active connected consumers.

  • POSTStarts data distribution for a package.
  • POSTStops data distribution for a package.
  • POSTSee that status of messages distribution.

Starts data distribution for a package.

post
Body
packageIdinteger · int32Required
userNamestring · min: 1Required
passwordstring · min: 1Required
Responses
200
Success
post
POST /Distribution/Start HTTP/1.1
Host: stm-api.lsports.eu
Content-Type: application/json-patch+json
Accept: */*
Content-Length: 51

{
  "packageId": 1,
  "userName": "text",
  "password": "text"
}
200

Success

No content

Stops data distribution for a package.

post
Body
packageIdinteger · int32Required
userNamestring · min: 1Required
passwordstring · min: 1Required
Responses
200
Success
post
POST /Distribution/Stop HTTP/1.1
Host: stm-api.lsports.eu
Content-Type: application/json-patch+json
Accept: */*
Content-Length: 51

{
  "packageId": 1,
  "userName": "text",
  "password": "text"
}
200

Success

{
  "header": {
    "httpStatusCode": 1,
    "errors": [
      {
        "message": "text"
      }
    ]
  },
  "body": {
    "message": "text"
  }
}

See that status of messages distribution.

post
Body
packageIdinteger · int32Required
userNamestring · min: 1Required
passwordstring · min: 1Required
Responses
200
Success
post
POST /Package/GetDistributionStatus HTTP/1.1
Host: stm-api.lsports.eu
Content-Type: application/json-patch+json
Accept: */*
Content-Length: 51

{
  "packageId": 1,
  "userName": "text",
  "password": "text"
}
200

Success

{
  "header": {
    "httpStatusCode": 1,
    "errors": [
      {
        "message": "text"
      }
    ]
  },
  "body": {
    "isDistributionOn": true,
    "consumers": [
      "text"
    ],
    "numberMessagesInQueue": 1,
    "messagesPerSecond": 1
  }
}