GrassBlade LRS API Documentation
This is the complete API documentation for connecting to the GrassBlade LRS 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 GrassBlade LRS: Query learning records and xAPI statements. Keep reading to get started.
Quickstart
Before you run your first GrassBlade LRS request, you need three things:
- A MindCloud account — sign in or create an account at MindCloud.
- A MindCloud API Key — create one in API Keys. Keep it on your server.
- At least one GrassBlade LRS connection — create or choose one in Connections. Note its
connectionId.
Every GrassBlade LRS action uses the same URL pattern:
https://connect.mindcloud.co/v1/universal/grassBladeLRS/latest/actions/{actionSlug}You need a MindCloud API Key and a GrassBlade LRS connection. Then call an action such as Get About:
curl --request GET \
--url "https://connect.mindcloud.co/v1/universal/grassBladeLRS/latest/actions/get-about" \
--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 GrassBlade LRS account that should run the action. MindCloud stores and refreshes the GrassBlade LRS 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.
GrassBlade LRS actions
All 33 published actions for this GrassBlade LRS version. Each page documents the endpoint, arguments, and response controls.
- POSTCreate Activity Profile
- POSTCreate Agent Profile
- POSTCreate State Document
- POSTCreate Statement
- POSTCreate Statement Batch
- PUTCreate Statement By ID
- DELETEDelete Activity Profile
- DELETEDelete Agent Profile
- DELETEDelete All State For Context
- DELETEDelete State Document
- GETGet About
- GETGet Activity By ID
- GETGet Activity Profile
- GETGet Agent Profile
- GETGet Person By Agent
- GETGet State Document
- GETGet Statement By ID
- GETGet Voided Statement
- GETList Activity Profile IDs
- GETList Activity Profile IDs Since
- GETList Agent Profile IDs
- GETList Agent Profile IDs Since
- GETList State IDs
- GETList State IDs Since
- GETList Statements
- PUTReplace Activity Profile
- PUTReplace Agent Profile
- PUTReplace State Document
- GETSearch Statements By Activity
- GETSearch Statements By Agent
- GETSearch Statements By Registration
- GETSearch Statements By Time Window
- GETSearch Statements By Verb
Related apps
More Human Resources apps on the Universal API, behind the same REST shape. Or browse all apps.