DivvyHQ API Documentation

This is the complete API documentation for connecting to the DivvyHQ 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 DivvyHQ: DivvyHQ is a content planning and production workflow platform for marketing and content teams. This app connects to DivvyHQ's Enterprise Accounts API for calendars, content items, campaigns, production tasks, team members, and related workflow data. Keep reading to get started.

Quickstart

Before you run your first DivvyHQ request, you need three things:

1. A MindCloud account — sign in or create an account at MindCloud.
2. A MindCloud API Key — create one in API Keys. Keep it on your server.
3. At least one DivvyHQ connection — create or choose one in Connections. Note its connectionId.

Every DivvyHQ action uses the same URL pattern:

https://connect.mindcloud.co/v1/universal/divvyHQ/latest/actions/{actionSlug}

You need a MindCloud API Key and a DivvyHQ connection. Then call an action such as Get Base Calendar:

curl --request GET \
  --url "https://connect.mindcloud.co/v1/universal/divvyHQ/latest/actions/get-base-calendar" \
  --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 DivvyHQ account that should run the action. MindCloud stores and refreshes the DivvyHQ 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.

DivvyHQ actions

All 33 published actions for this DivvyHQ version. Each page documents the endpoint, arguments, and response controls.

• POSTCreate Campaign
• POSTCreate Content Item
• POSTCreate Production Task
• POSTCreate Simple Calendar
• GETGet Base Calendar
• GETGet Calendar Entry
• GETGet Campaign
• GETGet Content Item
• GETGet My Profile
• GETGet Parent Calendar
• GETGet Production Task
• GETGet Role In Calendar
• GETGet Simple Calendar
• GETGet Team Member
• GETList Allowed Content Types In Calendars
• GETList Base Calendars
• GETList Calendar Entries
• GETList Campaigns
• GETList Content Items
• GETList Parent Calendars
• GETList Production Tasks
• GETList Roles In Calendars
• GETList Team Members
• PUTPatch Allowed Content Type In Calendar
• PUTPatch Campaign
• PUTPatch Content Item
• PUTPatch Production Task
• PUTPatch Simple Calendar
• GETSearch Calendar Entries
• PUTUpdate Campaign
• PUTUpdate Content Item
• PUTUpdate Production Task
• PUTUpdate Simple Calendar

Related apps

More Marketing apps on the Universal API, behind the same REST shape. Or browse all apps.

Google FormsMailchimpCalendlyWebflowGoogle AdsActiveCampaignBrevoMailerLite