> 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.md).

# API reference

Every operation of the four client-facing layers.

| Layer                                                                                            | Base URL                                                   | What it is for                                                                                                                                                                                           |
| ------------------------------------------------------------------------------------------------ | ---------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [Connect API](/api-reference/connect-api.md)                                                     | `https://<client-name>.mymedtrics.com/connect`             | The long-term public contract. A trusted outside system reads and partially writes one tenant's institution data under scoped, expiring, display-once credentials.                                       |
| [Medtrics Classic SIS Bridge (Compatibility API)](/api-reference/medtrics-classic-sis-bridge.md) | `https://<client-name>.mymedtrics.com/api-banner and /api` | Keeps an SIS integration written against Medtrics Classic running after the client moves to Oracle, with a bounded set of changes instead of a rewrite.                                                  |
| [GraphQL gateway](/api-reference/graphql-gateway.md)                                             | `https://<client-name>.mymedtrics.com/graphql/v1`          | Read-only query API over the same data as Connect (programs, rotations, evaluations) plus the integrations hub (catalog, enabled integrations, LTI platforms, health, audit), with the same credentials. |
| [LTI 1.3](/api-reference/lti-1.3.md)                                                             | `https://<client-name>.mymedtrics.com/lti`                 | Lets an LMS launch Medtrics as a tool and receive grades back.                                                                                                                                           |

Most integrations use the Connect API only. The GraphQL gateway manages the integration itself (keys, audit log, health); LTI 1.3 is for an LMS launching Medtrics; the Medtrics Classic SIS Bridge is a temporary layer for integrations written against Medtrics Classic.


---

# 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.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.