Actions7
Overview
This node integrates with the Betfair Australia API to retrieve information about horse-racing venues. Specifically, the "List Venues" operation fetches a list of active horse-racing venues based on optional filtering criteria. This is useful for users who want to programmatically access venue data for betting, sports analytics, or event management related to Australian horse racing.
Practical examples include:
- Fetching all currently active horse-racing venues in Australia.
- Filtering venues by name or associated events to narrow down selections.
- Using venue data as part of a larger workflow that analyzes races or places bets.
Properties
| Name | Meaning |
|---|---|
| Filters | A collection of optional filters to refine the venues returned. These include: - Event Type ID(s): Comma-separated IDs (e.g., "7" for Horse Racing). - Event ID(s): Comma-separated event IDs. - Competition ID(s): Comma-separated competition IDs. - Market Country Code(s): Comma-separated 2-letter country codes (default "AU"). - Market Type Code(s): Comma-separated market type codes. - Venue(s): Comma-separated venue names to filter by. - Text Query: Free-text search string for event or competition names. - Market Start From / To: Date/time range to filter markets starting within this period. - BSP Offered Only: Boolean to return only markets with Betfair Starting Price available. - In-Play Enabled Only: Boolean to return only markets that will turn in-play. - In-Play Now Only: Boolean to return only markets currently in-play. - Market Betting Type: One of Odds, Line, Asian Handicap Double Line, Asian Handicap Single Line. - With Orders: Filter by order status such as Pending, Executable, Execution Complete, Expired. - Race Type: Filter by race type including Thoroughbred Flat, Harness, Hurdle, Steeple, or No Filter. |
Output
The node outputs an array of JSON objects representing venues matching the specified filters. Each object corresponds to a venue and contains details as provided by the Betfair Australia API. The exact structure depends on the API response but typically includes venue identifiers, names, and possibly associated metadata.
No binary data output is produced by this operation.
Dependencies
- Requires valid Betfair Australia API credentials, including an application key and user login (username and password).
- The node performs authentication via the Betfair Australia identity service before making API calls.
- Network connectivity to Betfair Australia API endpoints is necessary.
- No additional external dependencies beyond the included HTTP client library.
Troubleshooting
- Authentication Failures: If login fails, ensure that the API credentials (app key, username, password) are correct and have appropriate permissions. Error messages from the API will be surfaced.
- Empty Results: If no venues are returned, verify that the filters applied are not overly restrictive or incorrect (e.g., invalid event or competition IDs).
- API Request Errors: Network issues or API downtime can cause request failures. Check connectivity and retry later.
- Invalid Input: Comma-separated lists must be properly formatted without trailing commas or spaces. Dates must be valid ISO date strings.
- Timeouts: The node uses a 15-second timeout for API requests; slow responses may cause errors.