with SurveyCTO and BingX?
Emit new event each time a new form submission is received in SurveyCTO. See the documentation. Note: The role of the authenticated user must "Allow server API access".
Get Perpetual Swap Account Asset Information See the documentation
Calculate leveraged position based on entry, stop price and account balance
Make any API call for Bingx Futures as per the documentation. See the documentation
The SurveyCTO API enables automated interactions with SurveyCTO services, a platform focusing on data collection and organization for research and survey projects. With this API, you can seamlessly retrieve, push, and manage survey data. Integrating SurveyCTO with Pipedream opens a realm of possibilities for automating data workflows, such as triggering actions based on new survey submissions, syncing collected data with other databases or apps, or even automating reports and notifications.
import { axios } from "@pipedream/platform"
export default defineComponent({
props: {
surveycto: {
type: "app",
app: "surveycto",
}
},
async run({steps, $}) {
// Please replace {{your_form_id}} with a valid form ID for testing.
return await axios($, {
url: `https://${this.surveycto.$auth.servername}.surveycto.com/api/v2/forms/data/wide/json/{{your_form_id}}`,
auth: {
username: `${this.surveycto.$auth.email}`,
password: `${this.surveycto.$auth.password}`,
},
params: {
date: `0`,
},
})
},
})
The BingX API offers a digital asset trading platform that enables users to perform crypto trades, access market data, and manage their portfolio. By leveraging this API on Pipedream, you can automate your cryptocurrency trading strategies, synchronize your trading data with other financial tools, and create real-time alerts based on market conditions.
import { axios } from '@pipedream/platform';
export default defineComponent({
props: {
bingx: {
type: "app",
app: "bingx",
}
},
async run({steps, $}) {
// Requires a dynamic signature generated for each request at runtime.
// please see conversation here: https://github.com/PipedreamHQ/pipedream/issues/4363
},
})