CueGrowth API Documentation
This is the complete API documentation for connecting to the CueGrowth API using MindCloud's Universal API. If you are new to MindCloud, start with the Introduction to see how one API can sit in front of many different apps.
MindCloud is an integration company that offers one normalized API to access 3,100+ apps from a single place. It cleans up provider-specific quirks, keeps requests and responses consistent, and centralizes authentication so you do not need to manage separate flows for every app. Browse other apps.
Meet CueGrowth: CueGrowth helps B2B teams automate LinkedIn outreach, lead generation, campaign management, messaging, and webhook-driven integrations through its public API. Keep reading to get started.
Quickstart
Before you run your first CueGrowth request, you need three things:
- A MindCloud account — sign in or create an account at MindCloud.
- A MindCloud API Key — create one in API Keys. Keep it on your server.
- At least one CueGrowth connection — create or choose one in Connections. Note its
connectionId.
Every CueGrowth action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/cueGrowth/latest/actions/{actionSlug}You need a MindCloud API Key and a CueGrowth connection. Then call an action such as Get Campaign By Id:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/cueGrowth/latest/actions/get-campaign-by-id" \
--header "Authorization: Bearer $MINDCLOUD_API_KEY" \
--get \
--data-urlencode "connectionId=$CONNECTION_ID"Every response comes back in the same envelope, with your rows in a data array:
{
"success": true,
"data": [
{ "id": "1042", "name": "Ava" }
],
"meta": {}
}After your first request works, use Shape your requests to control arguments, pagination, filtering, fields, and errors.
Authentication
Authentication has two layers. Your MindCloud API Key authenticates the request to MindCloud, sent as a Bearer token in the Authorization header. The connectionId selects the connected CueGrowth account that should run the action. MindCloud stores and refreshes the CueGrowth credentials behind that connection, so you never send provider tokens with your requests.
Pass connectionId in the query string for GET and DELETE actions, and in the JSON body for POST, PUT, and PATCH actions. Keep your MindCloud API Key on your server; do not ship it in browser code, mobile apps, public repositories, or logs.
CueGrowth actions
All 22 published actions for this CueGrowth version. Each page documents the endpoint, arguments, and response controls.
- PUTAdd Receiver To Campaign
- PUTBulk Add Receivers To Campaign
- POSTCreate Webhook
- DELETEDelete Webhook
- GETGet Campaign By Id
- GETGet Inbox
- GETGet Task Status
- GETGet Webhook
- GETList Campaigns
- GETList Campaigns by Receiver
- GETList Connections
- GETList Inboxes
- GETList Messages
- GETList Users
- GETList Webhooks
- PUTRemove Receiver From Campaign
- GETRetrieve Receiver
- GETRetrieve User
- POSTSend Message To Inbox
- POSTSend Message To Receiver
- PUTUpdate Campaign
- PUTUpdate Webhook
Related apps
More Marketing apps on the Universal API, behind the same REST shape. Or browse all apps.