# Edusign integrations: courses and students

> Create a course, create a student and create a professor in Edusign, and start a workflow when Edusign sends “Course created”.

**Canonical page:** https://tray.ai/connectors/edusign-integrations/
**Categories:** Operations
**Connects through:** HTTP Connector

## Overview

Edusign is a digital attendance tool for schools and training providers, where students sign in to courses electronically and staff track absences and send documents for signature. Tray.ai connects to Edusign through the HTTP Connector, so your workflows can call the Edusign API alongside the rest of your stack.

## Use cases

### Courses

Read, create, update, and delete courses in Edusign from any Tray.ai workflow. The Edusign API covers calls such as create a course and list courses.

- Create a course
- List courses
- Update a course

### Students

Read, create, update, and delete students in Edusign from any Tray.ai workflow. The Edusign API covers calls such as create a student and list students.

- Create a student
- List students
- Update a student

### Professors

Read, create, update, and delete professors in Edusign from any Tray.ai workflow. The Edusign API covers calls such as create a professor and list professors.

- Create a professor
- List professors
- Update a professor

### Groups

Read, create, update, and delete groups in Edusign from any Tray.ai workflow. The Edusign API covers calls such as create a group and list groups.

- Create a group
- List groups
- Update a group

### Justified absences

Read, create, update, and delete justified absences in Edusign from any Tray.ai workflow. The Edusign API covers calls such as create a justified absence and list justified absences.

- Create a justified absence
- List justified absences
- Update a justified absence

### Edusign events

Start a Tray.ai workflow the moment something happens in Edusign. Edusign sends events such as course created and course edited to a Tray.ai webhook trigger.

- Course created
- Course edited
- Course deleted

## Challenges Tray.ai solves

### Keeping Edusign credentials out of logs

A raw API call usually means pasting a key or token into the request, where it ends up in step inputs, logs, and screenshots.

**How Tray.ai helps:** Store Edusign credentials once as a Tray.ai authentication and reference them from the HTTP Connector. Tray.ai masks authentication values in logs, so the secret never shows up in a step's input or output.

### Going from the Edusign API docs to a working call

Translating an example request from API docs into a workflow step means copying the method, URL, headers, and body by hand.

**How Tray.ai helps:** Paste a cURL example from the Edusign API docs into the HTTP Connector and Tray.ai fills in the method, URL, headers, and body for you.

### Handling files and non-JSON responses

Not every API answers in JSON. Some return XML, files, or binary data, or expect a multipart upload.

**How Tray.ai helps:** The HTTP Connector parses JSON and XML responses, returns files you can pass to the next step, and sends multipart form data for uploads.

## Frequently asked questions

### Does Tray.ai connect to Edusign?

Yes. Tray.ai connects to Edusign through the HTTP Connector, which calls the Edusign API directly. Any call the Edusign API documents can run as a step in a Tray.ai workflow.

### How does Tray.ai authenticate with Edusign?

The Edusign API uses a bearer token. You save it once as a Tray.ai authentication, and the HTTP Connector adds it to every request.

### Can I get a dedicated Edusign connector?

Edusign runs through the HTTP Connector rather than a dedicated connector. If your team wants one, the Tray.ai connector SDK can build a dedicated Edusign connector from the Edusign API.

## Learn more

- Intelligent Integration: https://tray.ai/platform/intelligent-ipaas/
- Merlin Agent Builder: https://tray.ai/platform/merlin-agent-builder/
- Agent Gateway for MCP: https://tray.ai/platform/agent-gateway/
- Book a demo: https://tray.ai/contact/