Reach360 API Documentation

This is the complete API documentation for connecting to the Reach360 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 Reach360: Manage Reach360 learners, groups, enrollments, and reports. Keep reading to get started.

Quickstart

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

Every Reach360 action uses the same URL pattern:

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

You need a MindCloud API Key and a Reach360 connection. Then call an action such as Get Activity Report:

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

Reach360 actions

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

• POSTAdd User To Group
• POSTCreate Group
• POSTCreate Invitation
• POSTCreate Webhook
• DELETEDelete Group
• DELETEDelete Invitation
• DELETEDelete User
• DELETEDelete Webhook
• POSTEnroll Group In Course
• POSTEnroll Group In Learning Path
• POSTEnroll User In Course
• POSTEnroll User In Learning Path
• GETGet Activity Report
• GETGet Course
• GETGet Course Report
• GETGet Group
• GETGet Invitation
• GETGet Learner Report
• GETGet Learning Path
• GETGet Learning Path Courses Report
• GETGet Learning Path Learners Report
• GETGet User
• GETGet Webhook
• POSTImport Course Completion
• GETList Courses
• GETList Group Users
• GETList Groups
• GETList Invitations
• GETList Learning Path Courses
• GETList Learning Paths
• GETList User Favorites
• GETList User Groups
• GETList Users
• GETList Webhooks
• DELETERemove User From Group
• DELETEUnenroll Group From Course
• DELETEUnenroll Group From Learning Path
• DELETEUnenroll User From Course
• DELETEUnenroll User From Learning Path
• PUTUpdate Group

Related apps

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

LinkedInClockifyConnecteamBambooHRTalentLMSCertifierZoho RecruitMemberVault