...
| Name | Type | Description |
|---|---|---|
| token | xsd:string | REQUIRED. More information concerning authorization in API introduction section |
| page | xsd:int | Determines offset of paginated data. Default value is 1 which means first page. |
| limit | xsd:int | Determines maximum number of returned records on page. Used in paginated data. Default value is 500. Possible values: 5, 10, 25, 50, 100, 250, 500 |
| timestamp | xsd:unix_timestamp | Selection date, format UNIX_TIMESTAMP. Only incidents messages that occurred or were updated after this timestamp will be returned. By default (if no parameter given) incidents from last 24 hours. |
| timestamp_to | xsd:unix_timestamp | Selection date, format UNIX_TIMESTAMP. Only incidents messages that occurred before this timestamp will be returned. |
| sport_id | xsd:int | Identifier of the sport. Allows incidents for the selected sport to be filtered |
| type | xsd:string | Determines type of message
|
| object_id | xsd:int | REQUIRED if you set object_type attribute! Identifier of the object depends on object type, e.g. if you choose an event as an object_type you should use event identificator. The complete list of possible seasons can be retrieved using the API resource: seasons.index |
| object_type | xsd:string | Possible object type:
|
Method calling examples
Link | Description |
|---|---|
| https://api.softnetsport.com/v2/trading-feed.xml?token={{YOUR_TOKEN}} | Returns all important messages for trading purposes from the last 24 hours in XML format |
| https://api.softnetsport.com/v2/trading-feed?token={{YOUR_TOKEN}} | Returns all important messages for trading purposes from the last 24 hours in JSON format |
https://api.softnetsport.com/v2/trading-feed.xml?token={{YOUR_TOKEN}}&sport_id=1 | Returns all important messages for trading purposes from the last 24 hours for basketball events |
...
| .trading-feed | |
|---|---|
| id | Unique identifier for the message |
| type | Possible value:
|
| source | Internal attribute, please dont use this attribute |
| ut | Information about the date and time of when the message was created. Format UNIX_TIMESTAMP. |
| ..data | |
| ...bet_stop | node available only if message type is bet_stop |
| object_id | Identifier of the object depends on object type, e.g. if you choose an event as an object_type you should use event identificator The complete list of possible seasons can be retrieved using the API resource: seasons.index The complete list of possible events can be retrieved using the API resource: events.index |
| object_type | Possible object type:
|
| action | Describes type of operation. For this message type, action attribute always has create value |
| betting_offer_ids | List of betting offers identifiers separated by a comma (e.g. 123,234,321). Possibility to input multiple identifiers, separated by comma. If empty value ALL betting offers for specified object_id should be suspended or closed. |
| betting_offer_status | The betting offers specified in betting_offer_ids attribute can receive following values:
|
| ...outcome_result | node available only if message type is bet_stopoutcome_result |
| ...betting_offer_rollback | node available only if message type is betting_offer_rollback |