Hub Planner API Documentation

This is the complete API documentation for connecting to the Hub Planner 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 Hub Planner: Hub Planner, now part of Milient Resource Management, provides resource planning, project scheduling, bookings, timesheets, vacations, groups, clients, and related resource management data through a REST API. Keep reading to get started.

Quickstart

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

Every Hub Planner action uses the same URL pattern:

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

You need a MindCloud API Key and a Hub Planner connection. Then call an action such as Get Billing Rate:

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

Hub Planner actions

All 30 published actions for this Hub Planner version. Each page documents the endpoint, arguments, and response controls.

• GETGet Billing Rate
• GETGet Booking
• GETGet Booking Category
• GETGet Client
• GETGet Event
• GETGet Holiday
• GETGet Project
• GETGet Project Group
• GETGet Resource
• GETGet Time Entry
• GETList Billing Rates
• GETList Booking Categories
• GETList Bookings
• GETList Clients
• GETList Events
• GETList Holidays
• GETList Project Groups
• GETList Projects
• GETList Resource Groups
• GETList Resources
• GETList Time Entries
• GETSearch Billing Rates
• GETSearch Booking Categories
• GETSearch Bookings
• GETSearch Clients
• GETSearch Events
• GETSearch Holidays
• GETSearch Projects
• GETSearch Resources
• GETSearch Time Entries

Related apps

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

Google CalendarNotionTypeformJira Software CloudSmartsheetCal.comWufooBasecamp