3.0 General

Contents:

• 3.1 Synchronous Requests Format
  • 3.1.1 HTTP persistent connections
• 3.2 Synchronous Responses Format
  • 3.2.1 HTTP Status Codes
  • 3.2.2 Envelope
  • 3.2.3 Rate Limits
• 3.3 Creating an Asynchronous Stream
• 3.4 Asynchronous Server Message Format
• 3.5 Asynchronous Client Message Format
• 3.6 Examples
  • 3.6.1 Login example
  • 3.6.2 Synchronous request example
  • 3.6.3 Asynchronous connection
  • 3.6.4 Receiving event offers
  • 3.6.5 Working with a betslip

We have made every effort to design an API that abides by the HTTP standard, and use widely-supported payload formats such as JSON. In addition, we adhere to REST design principles where practical.

The greatest advantage of following widely adopted standards is the availability of comprehensive client libraries in a wide variety of programming languages. In doing so, we hope to minimise the initial cost of integrating MollyBet API with your own software.