Props Feed
Description
This feed returns props and futures and their outcomes available for the general
public at Justbet.cx limited according to the
specified criteria. These moneylines, by default, have a delay of up to 10 minutes
which is lowerable to 5 minutes. If an affiliate or partner needs it lowered even
further a special key parameter can be provided on a case by case basis.
This XML cache system has been created in order to protect our resources from abuse
or misuse but, by no means, is intended to limit affiliates that need greater line
accuracy.
NOTE : At the moment, feeds are only available in XML format but upon request they
can be trasformed to CSV, RSS or other formats and depending on their popularity,
they will be documented here.
Request
|
Script Location
|
http://feeds.justbet.cx/xml/getLiveFeedProps.asp
|
|
Usage
|
This script should be run using a web browser or anything that can communicate via
the HTTP protocol – POST or GET.
|
|
Input
|
Eleven optional arguments in the URL query string – all of them can be empty
or zeroes. If not specified, default value will be used.
|
|
types
|
comma separated list of types or one type – this is a category
name (a.k.a Contest Type) used for Props and FuturesDefault:
” – empty stringType: list of strings
of up to 50 characters
|
|
graded
|
either ‘N’ (no), ‘Y’ (yes) or ‘B’ (both) to indicate if to not return graded props,
only graded props or both graded and ungraded respectivelyDefault:
‘B’Type: string of up to one character
|
|
popindex
|
either ‘Y’ (yes) or ‘N’ (no) to indicate whether to return the popularity index
or notDefault: ‘N’Type:
string of up to one character
|
|
fromminutes
|
number minutes in future or negative for pastDefault:
0Type: integer
|
|
tominutes
|
number minutes in future or negative for past – must be greater than fromminutes
and if both are zero, date to lookup defaults to onedateDefault:
0Type: integer
|
|
onedate
|
a single date to return prop results forDefault:
” – empty string – or current date if no other date related parameters
are specifiedType: date in YYYY-MM-DD format
|
|
begindate
|
an inclusive begin date to return results forDefault:
” – empty stringType: date in YYYY-MM-DD
format
|
|
enddate
|
an inclusive end date to return results forDefault:
” – empty stringType: date in YYYY-MM-DD
format
|
|
orderby
|
‘date desc’ (by prop/future date descending), ‘date asc’ (by prop/futur date ascending),
‘popindex desc’ (by popularity index descending), ‘popindex asc’ (by popularity
index ascending), ‘type desc’ (by type descending) or ‘type asc’ (by type ascending)Default: ‘type asc’Type:
string of up to 12 characters
|
|
limit
|
maximum number of results to return – if zero no limit is specifiedDefault:
0Type: positive integer
|
|
refresh
|
number of seconds to refresh XML data if already exists – minimum is 300 unless
special key parameter is sent as wellDefault: 600
(10 minutes)Type: positive integer
|
|
Notes
|
• All parameters documented here except refresh and orderby are used
to limit the returned list of lines and the information included in the XML
• If parameters aren’t in the required format then their default is used instead
• There are 5 date related parameters: fromminutes, tominutes, begindate,
enddate and onedate but only up to two should be used at a time so
the precedence for their use is as follows:
° If either fromminutes or tominutes or both are specified and they
both aren’t or default to zero and the later is greater than the former then they
are used to determine the dates used to limit the lines
° Otherwise, if both begin date (begindate) and end date (enddate)
are specified and the later is greater or equal to than the former then they are
used instead
° Otherwise, if onedate is specified then this single date is used
° Lastly, if no parameters are specified then fromminutes parameter defaults
to 5
• All dates are in the server timezone we use which is PST (GMT -8) or PDT (GMT
-7) depending on if daylight savings time is currently being used
• The popularity index are not all-time-records but pertain only to the scope defined
by your query – also you can only order by this index if you have set popindex=Y
• All parameters that are lists aren’t qualified – that is, they lack any
quotation marks
|
RESPONSE
The response is delivered in
XML format encoded in the
UTF-8 character set with a number of almost self explanatory tags which
are further described below:
NOTE : Errors aren’t reported in the XML itself since we attempt
to handle them internally as much as possible. However, we’d like to improve the
response so that certain common errors are reported so if a fatal error occurs that
prevents the XML from properly being displayed, please let us know.
|
Tag
|
Attributes
|
Description
|
|
livefeedprops
|
root tag – it’s attributes are the non-default parameters used to limit
the results
|
|
paramstr
|
this is used for debugging purposes only – the contents of the tag is the
string used to query the database
|
|
generator
|
by what means was the XML file generated? (currently only two possibilities: ASP
or automated VBS script)
|
|
generated
|
date in which the database was queried and the XML was generated
|
|
contest
|
one of these for each unique prop or future event returned
|
|
contestname
|
the name associated to the event
|
|
contesttype1
|
the primary contest type of the event
|
|
contesttype2
|
the secondary contest type of the event
|
|
contesttype3
|
the tertiary contest type of the event
|
|
contestdate
|
the date and time of the event
|
|
contestdow
|
the day of week of the event from 1 (Sunday) to 7 (Saturday)
|
|
wagercutoff
|
the date when wagers are no longer permited for this particular event
|
|
status
|
the status of the game
|
|
gradedate
|
the date when this event was graded – empty if it hasn’t been graded
|
|
contestant
|
one of these for each unique contestant returned in each prop or future event (contest)
|
|
contestnum
|
the unique number of the contest
|
|
contestantnum
|
the unique number of the contestant
|
|
rotnum
|
the rotation number assigned for this contestant
|
|
contestantname
|
the name of the contestant
|
|
moneyline
|
the line adjusted to this contestant
|
|
store
|
the store name associated to this contestant
|
|
outcome
|
the outcome for this particular contestant: ‘W’ for win, ‘L’ for loose and ” (empty)
for undefined
|
|
circled
|
is the moneyline circled? Y or N?
|
|
popularity
|
if requested, the popularity for the parent contest tag
|
|
index
|
the index associated to this event – 1 being the most popular (that is, with
most amount of wagers) and as the index increases, less popular
|