TBS Apps API

BlackbooksSearchRequest

The following routes are available for this service:
POST	/BlackbooksSearch	Search for blackbooks runners, for the currently authenticated user	Search blackbooks runners

**BlackbooksSearchRequest** Parameters:
Name	Parameter	Data Type	Required	Description
DisciplineType	body	string	No	Discipline type, for example: T – Thoroughbred, H – Harness and G – Greyhounds
Term	body	string	No	Search term

**BlackbooksSearchResponse** Parameters:
Name	Parameter	Data Type	Required
ErrorNo	form	int	No
Message	form	string	No
HorseList	form	List<BlackbooksHorse>	No

**BlackbooksHorse** Parameters:
Name	Parameter	Data Type	Required
Age	form	int?	No
Horse	form	string	No
Dam	form	string	No
Sire	form	string	No
Hyear	form	int?	No
HorseId	form	int?	No
DamId	form	int?	No
SireId	form	int?	No
Sex	form	string	No
Discipline	form	string	No
CourseName	form	string	No
RaceDate	form	string	No
CountryCode	form	string	No
CrsCountryCode	form	string	No
CourseId	form	int?	No
Lrfp	form	int?	No
RaceId	form	int?	No
RaceNo	form	double?	No
RaceName	form	string	No
Type	form	string	No
NextRunDate	form	string	No
NextCountryCode	form	string	No
NextCountryid	form	int?	No
NextCourseCode	form	string	No
NextCourseId	form	int?	No
NextCourse	form	string	No
NextMeetingId	form	int?	No
NextRaceId	form	int?	No
NextRace	form	string	No
NextRaceNo	form	double?	No
Abbreivation	form	List<string>	No

To override the Content-type in your clients, use the HTTP Accept Header, append the .xml suffix or ?format=xml

HTTP + XML

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /BlackbooksSearch HTTP/1.1 
Host: tstextweb20.np.bluebet.com.au 
Accept: application/xml
Content-Type: application/xml
Content-Length: length

<BlackbooksSearchRequest xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
  <DisciplineType>String</DisciplineType>
  <Term>String</Term>
</BlackbooksSearchRequest>

HTTP/1.1 200 OK
Content-Type: application/xml
Content-Length: length

<BlackbooksSearchResponse xmlns:i="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://schemas.datacontract.org/2004/07/TBS.Frontend.RequestLayer.RequestFunctions">
  <ErrorNo>0</ErrorNo>
  <HorseList xmlns:d2p1="http://schemas.datacontract.org/2004/07/TBS.Frontend.Messaging.DataContracts">
    <d2p1:BlackbooksHorse>
      <d2p1:Abbreivation xmlns:d4p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays">
        <d4p1:string>String</d4p1:string>
      </d2p1:Abbreivation>
      <d2p1:Age>0</d2p1:Age>
      <d2p1:CountryCode>String</d2p1:CountryCode>
      <d2p1:CourseId>0</d2p1:CourseId>
      <d2p1:CourseName>String</d2p1:CourseName>
      <d2p1:CrsCountryCode>String</d2p1:CrsCountryCode>
      <d2p1:Dam>String</d2p1:Dam>
      <d2p1:DamId>0</d2p1:DamId>
      <d2p1:Discipline>String</d2p1:Discipline>
      <d2p1:Horse>String</d2p1:Horse>
      <d2p1:HorseId>0</d2p1:HorseId>
      <d2p1:Hyear>0</d2p1:Hyear>
      <d2p1:Lrfp>0</d2p1:Lrfp>
      <d2p1:NextCountryCode>String</d2p1:NextCountryCode>
      <d2p1:NextCountryid>0</d2p1:NextCountryid>
      <d2p1:NextCourse>String</d2p1:NextCourse>
      <d2p1:NextCourseCode>String</d2p1:NextCourseCode>
      <d2p1:NextCourseId>0</d2p1:NextCourseId>
      <d2p1:NextMeetingId>0</d2p1:NextMeetingId>
      <d2p1:NextRace>String</d2p1:NextRace>
      <d2p1:NextRaceId>0</d2p1:NextRaceId>
      <d2p1:NextRaceNo>0</d2p1:NextRaceNo>
      <d2p1:NextRunDate>String</d2p1:NextRunDate>
      <d2p1:RaceDate>String</d2p1:RaceDate>
      <d2p1:RaceId>0</d2p1:RaceId>
      <d2p1:RaceName>String</d2p1:RaceName>
      <d2p1:RaceNo>0</d2p1:RaceNo>
      <d2p1:Sex>String</d2p1:Sex>
      <d2p1:Sire>String</d2p1:Sire>
      <d2p1:SireId>0</d2p1:SireId>
      <d2p1:Type>String</d2p1:Type>
    </d2p1:BlackbooksHorse>
  </HorseList>
  <Message>String</Message>
</BlackbooksSearchResponse>