BlueSnap ACTION
List Transactions
List BlueSnap transactions via the Reporting API. Report data is delayed by about one hour, so transactions from the last hour may not appear yet (use Get Transaction for a just-created transaction). Returns transaction summaries whose
Invoice ID field is the transactionId usable in Get Transaction and Refund Transaction. The output includes totalRowCount and, when more rows remain, a nextPageToken to pass back into this action for the next page. See the documentation- Action
- Read only
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's BlueSnap account once, then configure and run List Transactions 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: "bluesnap-list-transactions",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
bluesnap: { authProvisionId: "apn_xxxxxxx" },
period: "Period",
fromDate: "From Date",
},
})
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": "bluesnap-list-transactions",
"configured_props": {
"bluesnap": { "authProvisionId": "apn_xxxxxxx" },
"period": "Period",
"fromDate": "From Date"
}
}'// 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": "bluesnap",
},
},
},
)
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: "bluesnap-list-transactions",
arguments: {
period: "Period",
fromDate: "From Date",
},
})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 |
|---|---|---|
period Period | string | Reporting period covered by the report. Use CUSTOM together with From Date and To Date to report on an explicit range. Required |
fromDate From Date | string | Start date as MM/DD/YYYY (e.g. 01/01/2025). Required when period is CUSTOM. Optional |
toDate To Date | string | End date as MM/DD/YYYY (e.g. 12/31/2025). Required when period is CUSTOM. Optional |
limit Limit | integer | Maximum number of transactions to return (page size). Must be between 1 and 1000. Optional |
nextPageToken Next Page Token | string | The nextPageToken value returned by a previous run of this action, to fetch the following page. The token already encodes the original query, so Period, From Date, To Date, and Limit are ignored when it is set. Omit it for the first page. Optional |
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
- bluesnap-list-transactions
- Version
- 0.0.1
- App
- BlueSnap
- Authentication
- API key
- Read-only
- Yes
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗