Meisterplan API Documentation

This is the complete API documentation for connecting to the Meisterplan 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 Meisterplan: Coordinate people across teams and initiatives. Keep reading to get started.

Quickstart

Before you run your first Meisterplan 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 Meisterplan connection — create or choose one in Connections. Note its connectionId.

Every Meisterplan action uses the same URL pattern:

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

You need a MindCloud API Key and a Meisterplan connection. Then call an action such as Get Allocation:

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

Meisterplan actions

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

• POSTCreate Milestone
• POSTCreate Or Update Allocation
• POSTCreate Program
• POSTCreate Project
• POSTCreate Resource
• POSTCreate Role
• POSTCreate Team
• DELETEDelete Allocation
• DELETEDelete Milestone
• DELETEDelete Program
• DELETEDelete Project
• DELETEDelete Resource
• DELETEDelete Role
• DELETEDelete Team
• POSTFind Or Create Resources
• GETGet Allocation
• GETGet Milestone
• GETGet Program
• GETGet Project
• GETGet Resource
• GETGet Role
• GETGet Scenario
• GETGet Team
• GETList Allocations
• GETList Calendars
• GETList Milestones
• GETList Portfolios
• GETList Programs
• GETList Projects
• GETList Resources
• GETList Roles
• GETList Scenarios
• GETList Teams
• PUTUpdate Allocation
• PUTUpdate Milestone
• PUTUpdate Program
• PUTUpdate Project
• PUTUpdate Resource
• PUTUpdate Role
• PUTUpdate Team

Related apps

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

Google SheetsGmailSlackGoogle CalendarGoogle DriveNotionHubSpotGoogle Forms