Actions7
Overview
This node integrates with the Betfair Australia API to retrieve detailed market catalogues for betting markets. Specifically, the "List Market Catalogue" operation fetches market details and selections based on various filters and options. This is useful for users who want to explore available betting markets, their events, runners, and other metadata before placing bets or analyzing market data.
Common scenarios include:
- Fetching horse racing markets filtered by country, event type, or venue.
- Retrieving markets that are currently in-play or starting within a specific time window.
- Getting detailed descriptions of markets and runners to display in custom dashboards or betting tools.
Example: A user wants to list all horse racing markets in Australia starting today, including event and runner descriptions, sorted by the earliest start time.
Properties
| Name | Meaning |
|---|---|
| Filters | Collection of filters to narrow down the markets returned. Includes: - Event Type ID(s): Comma-separated IDs (e.g., "7" for Horse Racing). - Event ID(s): Comma-separated event identifiers. - 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 (e.g., "MATCH_ODDS", "WIN"). - Venue(s): Comma-separated venue names. - Text Query: Free-text search string for event or competition names. - Market Start From / To: Date/time range for market start times. - BSP Offered Only: Boolean to return only markets with Betfair Starting Price. - 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 (Pending, Execution Complete, Executable, Expired). - Race Type: Filter by race type (No Filter, Thoroughbred Flat, Harness, Hurdle, Steeple). |
| Market Catalogue Options | Collection of options controlling the market catalogue output: - Market Data to Return: Multi-select fields such as Competition, Event, Event Type, Market Description, Market Start Time, Runner Description, Runner Metadata. - Sort Order: How results are sorted (First to Start, Last to Start, Minimum/Maximum Available, Minimum/Maximum Traded). - Max Results: Number of results to return (1 to 1000, default 100). |
Output
The node outputs an array of JSON objects representing market catalogues matching the specified filters and options. Each object contains detailed information about a market, including:
- Event details (name, type, date/time)
- Market description and type
- Runner descriptions and metadata
- Competition and venue information (if requested)
- Market start time
The exact structure depends on the selected "Market Data to Return" projection but generally includes nested objects describing the event and its participants.
No binary data output is produced by this operation.
Dependencies
- Requires valid Betfair Australia API credentials including an application key, username, and password.
- The node performs authentication via the Betfair identity service to obtain a session token before making API calls.
- Uses the Axios HTTP client library for REST requests.
- Network access to Betfair Australia API endpoints is required.
Troubleshooting
- Authentication errors: If login fails, ensure the provided API credentials (app key, username, password) are correct and active. Error messages from the API are surfaced clearly.
- Missing required parameters: For this operation, filters can be empty but some filters like market IDs are mandatory for other operations. Ensure proper input is provided.
- API request failures: Network issues or invalid filter values may cause API errors. The node logs detailed error responses when available.
- Empty results: If no markets match the filters, the output will be an empty array. Adjust filters or increase max results if needed.
- Timeouts: The node uses a 15-second timeout for API calls; slow network or large queries might cause timeouts.