Edusign API Documentation

This is the complete API documentation for connecting to the Edusign 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 Edusign: Manage attendance, documents, surveys, and training operations. Keep reading to get started.

Quickstart

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

Every Edusign action uses the same URL pattern:

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

You need a MindCloud API Key and a Edusign connection. Then call an action such as Get Course By ID:

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

Edusign actions

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

• POSTAdd Students Or Professors To Training
• DELETEArchive Professor
• DELETEArchive Student
• DELETEArchive Training
• POSTCreate Course
• POSTCreate Document Using Base64
• POSTCreate Event
• POSTCreate Professor
• POSTCreate Student
• POSTCreate Survey
• POSTCreate Training
• DELETEDelete Course
• GETGet Course By ID
• GETGet Course ID By API ID
• GETGet Course PIN
• GETGet Course Timestamps
• GETGet Document By ID
• GETGet Professor By Email
• GETGet Professor By ID
• GETGet Professor ID By API ID
• GETGet School
• GETGet Student By Email
• GETGet Student By ID
• GETGet Student ID By API ID
• GETGet Survey By ID
• GETGet Training
• GETList Courses
• GETList Document Templates
• GETList Documents
• GETList Events
• GETList Professors
• GETList Students
• GETList Students by IDs
• GETList Surveys
• GETList Trainings
• PUTUpdate Course
• PUTUpdate Professor
• PUTUpdate School
• PUTUpdate Student
• PUTUpdate Training

Related apps

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

LinkedInClockifyConnecteamBambooHRTalentLMSCertifierZoho RecruitMemberVault