> 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/get-started.md).

# Get started

Token, conventions, workflows, Postman: the path to a first integration.

Three steps take an integration from credentials to its first scheduled sync.

1. [Quickstart](/get-started/quickstart.md) — exchange your API app's credentials for a token and make the first call to `https://<client-name>.mymedtrics.com/connect`.
2. [Conventions](/get-started/conventions.md) — the rules every call follows: `Medtrics-API-Date`, idempotency keys, webhook signatures and retries, rate limits, hosting.
3. [Admin workflows](/get-started/admin-workflows.md) — pick the job you are automating (nightly learner sync, rotation publish, score import…) and take its operations and scopes from there.

No tenant to test against yet? The [Sandbox](/get-started/sandbox.md) at `https://sandbox.mymedtrics.com` runs the same API on demo data with a sandbox key instead of a token — ask <help@medtrics.com> for one. [Postman](/get-started/postman.md) holds the same calls as a collection, if you would rather try them before writing code.

Moving from Medtrics Classic? The [Classic data mapping](/get-started/classic-data-mapping.md) shows where each of its tables and fields lands in Oracle, and the [Medtrics Classic SIS Bridge](/api-reference/medtrics-classic-sis-bridge.md) keeps an SIS integration written against the Classic API running while you move it to Connect.


---

# 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/get-started.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.