View as Markdown
BitMEX icon

BitMEX TRIGGER

New Executed Trade

Emit new event when a balance‑affecting execution (trade fill, settlement, realized PnL) occurs in your BitMEX account. See the documentation
  • Trigger
  • Polling
  • API key
  • Webhook delivery

IMPLEMENTATION

Deploy this event source

Connect the user's BitMEX account, configure the source, and choose the webhook where your backend receives events.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const deployed = await pd.triggers.deploy({
  id: "bitmex-new-executed-trade",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    bitmex: { authProvisionId: "apn_xxxxxxx" },
    timer: { "intervalSeconds": 900 },
    targetAccountId: 10,
  },
  webhookUrl: "https://example.com/webhooks/bitmex",
})

console.log(deployed.id)

MCP exposes on-demand actions. Event sources are deployed through the Connect SDK or API because they continue listening after the initial request.

SCHEMA

Configuration

These inputs define which events the source watches. Dynamic options are loaded from the connected account.

New Executed Trade configuration
Property Type Description
timer Timer $.interface.timer
Required
targetAccountId Target Account ID integer
AccountId fetching the trade history, must be a paired account with main user
Required
symbol Symbol string
Instrument symbol. Send a bare series (e.g. XBT) to get data for the nearest expiring contract in that series. You can also send a timeframe, e.g. XBT:quarterly. Timeframes are nearest, daily, weekly, monthly, quarterly, biquarterly, and perpetual. Symbols are case-insensitive.
Optional Dynamic

01

Connect

Your user authorizes BitMEX through Pipedream managed auth.

02

Deploy

Your backend deploys this source with that user's own configuration.

03

Webhook delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source — after each poll.

OR

On-demand retrieval

No webhook required. Your app or agent can fetch recent events from the trigger events API.

Registry key
bitmex-new-executed-trade
Version
0.0.1
App
BitMEX
Authentication
API key
Delivery
Polling source
Output
Events emitted by BitMEX.