# New Executed Trade — BitMEX

> Emit new event when a balance‑affecting execution (trade fill, settlement, realized PnL) occurs in your BitMEX account. See the documentation

- Key: `bitmex-new-executed-trade`
- Type: Trigger (Polling)
- Version: 0.0.1
- App: BitMEX (`bitmex`) — https://pipedream.com/apps/bitmex.md
- This page (HTML): https://pipedream.com/apps/bitmex/triggers/new-executed-trade
- Source: https://github.com/PipedreamHQ/pipedream/blob/master/components/bitmex/sources/new-executed-trade/new-executed-trade.mjs

## Description

Emit new event when a balance‑affecting execution (trade fill, settlement, realized PnL) occurs in your BitMEX account. [See the documentation](https://www.bitmex.com/api/explorer/#!/Execution/Execution_getTradeHistory)

## Props

| Prop | Type | Required | Description |
|---|---|---|---|
| `timer` | `$.interface.timer` | Yes | Timer |
| `targetAccountId` | `integer` | Yes | AccountId fetching the trade history, must be a paired account with main user |
| `symbol` | `string` | No | 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. Options are loaded from the connected account. |

## Returns

Events emitted by BitMEX.

## Run it

**TypeScript**

```ts
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)
```

**cURL**

```bash
curl -X POST https://api.pipedream.com/v1/connect/{project_id}/triggers/deploy \
  -H "Content-Type: application/json" \
  -H "X-PD-Environment: production" \
  -H "Authorization: Bearer {access_token}" \
  -d '{
    "external_user_id": "{external_user_id}",
    "id": "bitmex-new-executed-trade",
    "webhook_url": "https://example.com/webhooks/bitmex",
    "configured_props": {
      "bitmex": { "authProvisionId": "apn_xxxxxxx" },
      "timer": { "intervalSeconds": 900 },
      "targetAccountId": 10
    }
  }'
```

**MCP**

MCP servers expose BitMEX actions as on-demand tools.

New Executed Trade is an event source, so your application deploys it with the Connect SDK or API and then either receives each event at a webhook URL or retrieves events on demand with the trigger events API.

## Event delivery

Every event is sent to the HTTP endpoint you choose when you deploy the source. Or: no webhook required — your app or agent can fetch recent events from the [trigger events API](https://pipedream.com/docs/connect/api-reference/list-trigger-events.md) instead.

---

- App: https://pipedream.com/apps/bitmex.md · All apps: https://pipedream.com/apps