Actions7
Overview
This node integrates with the Betfair Australia API to retrieve various types of betting-related data. Specifically, the "List Current Orders" operation fetches the user's current bet orders from their Betfair account. This is useful for users who want to monitor or analyze their active bets programmatically within an n8n workflow.
Common scenarios include:
- Tracking all currently placed bets to update dashboards or trigger alerts.
- Filtering bets by specific markets or bet IDs to focus on particular events.
- Sorting and paginating through large numbers of bets for detailed analysis.
For example, a user could list all executable (active) bets placed in the last week on horse racing markets, sorted by the time they were placed, to assess their current exposure.
Properties
| Name | Meaning |
|---|---|
| Filter by Bet IDs | Comma-separated list of Bet IDs to filter the current orders by specific bets. |
| Filter by Market IDs | Comma-separated list of Market IDs to filter orders related to specific markets. |
| Order Projection | Type of orders to return: All Orders, Executable Orders (active), or Execution Complete Orders. |
| Placed Date From | Start date/time to filter orders placed after this timestamp. |
| Placed Date To | End date/time to filter orders placed before this timestamp. |
| Order By | Field to sort the results by: Bet ID, Market, Match Time, Place Time, Settled Time, or Void Time. |
| Sort Direction | Sort order direction: Latest to Earliest or Earliest to Latest. |
| From Record (Pagination) | Starting record index for pagination (zero-based). |
| Record Count (Pagination) | Number of records to return (max 1000). |
Output
The output is a JSON array where each item represents a current order (bet) retrieved from the Betfair Australia API. Each JSON object contains detailed information about a bet, such as its identifiers, status, placement time, market details, and other relevant metadata as provided by the API.
No binary data is output by this node.
Dependencies
- Requires valid Betfair Australia API credentials including an application key, username, and password.
- The node performs an authentication request to obtain a session token before making API calls.
- Uses the Betfair Australia REST API endpoints for login and fetching betting data.
- Network connectivity to
https://identitysso.betfair.com.au/api/loginandhttps://api.betfair.com.au/exchange/betting/rest/v1.0/.
Troubleshooting
- Authentication Failures: If login fails, errors like "No token received" or API error messages will be thrown. Ensure that the API credentials are correct and have necessary permissions.
- Missing Required Parameters: For example, if no Market IDs are provided when required, the node throws an error indicating missing inputs.
- API Request Errors: Network issues or invalid parameters may cause HTTP errors. The node surfaces these with detailed messages including API response data when available.
- Pagination Limits: The maximum number of records per request is capped at 1000; requesting more may result in truncated results.
- Empty Results: If filters are too restrictive, the returned array may be empty.
To resolve common errors:
- Double-check credential correctness.
- Verify that required fields like Market IDs or Bet IDs are properly formatted and non-empty.
- Adjust filters and pagination settings to ensure valid queries.
- Review API rate limits and network connectivity.