Bitget ACTION
Spot - Trade - Get Fills
Retrieve transaction details (fills) for a user. See the documentation
- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Bitget account once, then configure and run Spot - Trade - Get Fills from your backend or agent.
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 result = await pd.actions.run({
id: "bitget-spot-trade-get-fills",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
bitget: { authProvisionId: "apn_xxxxxxx" },
symbol: "Symbol",
orderId: "Order ID",
},
})
console.log(result)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "bitget-spot-trade-get-fills",
"configured_props": {
"bitget": { "authProvisionId": "apn_xxxxxxx" },
"symbol": "Symbol",
"orderId": "Order ID"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "bitget",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "bitget-spot-trade-get-fills",
arguments: {
symbol: "Symbol",
orderId: "Order ID",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| Property | Type | Description |
|---|---|---|
symbol Symbol | string | Trading pair symbol Optional Dynamic |
orderId Order ID | string | Order ID Optional Dynamic |
startTime Start Time | string | The record start time for the query. Unix millisecond timestamp, e.g. 1690196141868 Optional |
endTime End Time | string | The end time of the record for the query. Unix millisecond timestamp, e.g. 1690196141868 Optional |
limit Limit | integer | Default: 100, maximum: 100. Optional |
idLessThan ID Less Than | string | Requests the content on the page before this ID (older data), the value input should be the tradeId of the corresponding interface. Optional Dynamic |
REFERENCE
Tool details
Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.
- Registry key
- bitget-spot-trade-get-fills
- Version
- 0.0.3
- App
- Bitget
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗