Actions46
- Account Actions
- Alcor Exchange (DEX) Actions
- Asset Actions
- Governance Actions
- History Actions
- Marketplace (AtomicMarket) Actions
- Nefty (Blends & Packs) Actions
- Smart Contract Action Actions
- Token Actions
Alcor Exchange (DEX) → Get Active Orders
AI-generatedSummary
Fetches the active (open) orders on an Alcor Exchange DEX market for a WAX account. The source pack shows only an obfuscated entry module and a license check, so the exact query and return shape can't be confirmed.
Inputs
- endpoint (required) — WAX API endpoint to use. Choices: Greymass (default), EOS Nation, EOSphere, Pink.gg, WAX Sweden, or Custom.
- customEndpoint — Custom WAX API URL. Shown only when Endpoint is Custom.
- marketId (required) — Numeric ID of the Alcor trading pair market to look up orders on.
- account — WAX account to fetch orders for. Per the field description, it defaults to the credential account when left empty.
- authorization — Actor and permission (active, owner or custom) entries. They are declared for all Alcor operations and mainly matter for signed actions, so they are likely unused when reading orders.
Output shape
One output item per input item. The item's json holds the active orders for the given market and account.
The source is obfuscated and the resource handler module is not included, so the exact fields can't be verified. The node requires the waxKitPrivateKeyApi credential and runs a license-key check (Lemon Squeezy) before executing. With Continue On Fail enabled, a failing item returns json with success:false, error and details. Otherwise the error is thrown.
Examples
Example 1: List open orders for the credential account on a market
Endpoint: Greymass; Market ID: 1; Account: empty (falls back to the credential account).
Example 2: Check another account's open orders on a custom node
Endpoint: Custom with a Custom Endpoint URL; Market ID: 5; Account: the target WAX account name.