> For the complete documentation index, see [llms.txt](https://docs.mymedtrics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mymedtrics.com/api-reference/connect-api.md).

# Connect API

REST reference: every resource, operation, scope and schema.

Public REST contract for Medtrics Connect partner integrations. Medtrics-API-Date selects the request contract. Rotation creates with 2026-10-27 require clinical\_schedule\_id and block\_id; previously accepted dates preserve optional placement references through compatibility handling.

```
https://<client-name>.mymedtrics.com/connect/<resource>
Authorization: Bearer <access token>
Medtrics-API-Date: 2026-10-27
```

62 paths, 99 operations, grouped by resource in the pages below; the required scope is shown on each operation. New here? Start with the [Quickstart](/get-started/quickstart.md). The machine-readable contract is [openapi.yaml](https://medtricslab.gitbook.io/medtricslab-docs/api-reference/connect-api/oauth).

| Resource                | Operations |
| ----------------------- | ---------- |
| OAuth                   | 1          |
| Programs                | 2          |
| Roles                   | 2          |
| Group Leader Roles      | 6          |
| Group Tags              | 6          |
| Groups                  | 10         |
| Academic Periods        | 2          |
| Blocks                  | 5          |
| Scores                  | 5          |
| ExamScores              | 5          |
| Rotation Definitions    | 6          |
| Curriculum              | 3          |
| Graded Course Rotations | 3          |
| Case Templates          | 2          |
| Case Logs               | 2          |
| Clinical Schedules      | 7          |
| Sites                   | 2          |
| Learners                | 12         |
| Rotations               | 7          |
| Evaluations             | 2          |
| Advancements            | 3          |
| Imports                 | 1          |
| Webhooks                | 5          |


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.mymedtrics.com/api-reference/connect-api.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.