Maildroppa API Documentation
This is the complete API documentation for connecting to the Maildroppa 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 Maildroppa: Official Maildroppa API (Beta) wrapper for subscribers, segments, tags, field types, and signup forms. Keep reading to get started.
Quickstart
Before you run your first Maildroppa 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 Maildroppa connection — create or choose one in Connections. Note its
connectionId.
Every Maildroppa action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/maildroppa/latest/actions/{actionSlug}You need a MindCloud API Key and a Maildroppa connection. Then call an action such as Count Filtered Subscribers:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/maildroppa/latest/actions/count-filtered-subscribers" \
--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 Maildroppa account that should run the action. MindCloud stores and refreshes the Maildroppa 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.
Maildroppa actions
All 36 published actions for this Maildroppa version. Each page documents the endpoint, arguments, and response controls.
- PUTAdd Subscriber Tag By Email
- PUTAdd Subscriber Tag By ID
- GETCount Filtered Subscribers
- GETCount Subscribers
- POSTCreate Double Opt-In Subscriber
- POSTCreate Segment
- POSTCreate Subscriber
- POSTCreate Subscriber Field
- POSTCreate Tag
- DELETEDelete Segment
- DELETEDelete Subscriber
- DELETEDelete Subscriber By Email
- DELETEDelete Subscriber Field
- DELETEDelete Subscriber Field By Email
- DELETEDelete Subscriber Field By ID
- DELETEDelete Subscriber Tag By Email
- DELETEDelete Subscriber Tag By ID
- DELETEDelete Subscribers
- DELETEDelete Subscribers By Status
- DELETEDelete Tag
- GETGet Segment
- GETGet Subscriber
- GETList Field Matchers
- GETList Filtered Subscribers
- GETList Segments
- GETList Signup Forms
- GETList Subscriber Fields
- GETList Subscribers
- GETList Tags
- PUTUpdate Segment
- PUTUpdate Subscriber
- PUTUpdate Subscriber Email
- PUTUpdate Subscriber Field
- PUTUpdate Tag
- PUTUpsert Subscriber Field By Email
- PUTUpsert Subscriber Field By ID
Related apps
More Marketing apps on the Universal API, behind the same REST shape. Or browse all apps.