Resource Guru API Documentation

This is the complete API documentation for connecting to the Resource Guru 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 Resource Guru: Connect Resource Guru to read and manage accounts, resources, bookings, clients, projects, time off, timesheets, custom fields, reports, and webhooks through the official OAuth2 API. Keep reading to get started.

Quickstart

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

Every Resource Guru action uses the same URL pattern:

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

You need a MindCloud API Key and a Resource Guru connection. Then call an action such as Get Booking:

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

Resource Guru actions

All 52 published actions for this Resource Guru version. Each page documents the endpoint, arguments, and response controls.

• POSTCreate Booking
• POSTCreate Client
• POSTCreate Custom Field
• POSTCreate Project
• POSTCreate Resource
• POSTCreate Timesheet
• POSTCreate Webhook
• DELETEDelete Booking
• DELETEDelete Client
• DELETEDelete Custom Field
• DELETEDelete Project
• DELETEDelete Resource
• DELETEDelete Webhook
• PUTDismiss Timesheet
• GETGet Booking
• GETGet Client
• GETGet Current User
• GETGet Custom Field
• GETGet Project
• GETGet Resource
• GETGet Resource Type
• GETGet User
• GETGet Webhook
• PUTInvite Resource
• GETList Activity Types
• GETList Archived Clients
• GETList Archived Projects
• GETList Archived Resources
• GETList Booking Activities
• GETList Bookings
• GETList Client Bookings
• GETList Clients
• GETList Custom Fields
• GETList Project Bookings
• GETList Projects
• GETList Resource Bookings
• GETList Resource Types
• GETList Resources
• GETList Timesheets
• GETList Users
• GETList Webhooks
• PUTRemind Booking
• PUTResolve Booking
• PUTSplit Booking
• PUTTest Webhook
• PUTUpdate Booking
• PUTUpdate Client
• PUTUpdate Custom Field
• PUTUpdate Project
• PUTUpdate Resource
• PUTUpdate Timesheet
• PUTUpdate Webhook

Related apps

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

Google SheetsGmailSlackGoogle CalendarGoogle DriveNotionHubSpotGoogle Forms