> 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/medtrics-classic-sis-bridge/sites.md). # Sites ## GET /api-banner/sites/ > ```json {"openapi":"3.1.0","info":{"title":"Medtrics Legacy SIS Bridge (Compatibility API)","version":"draft-2026-10-29"},"servers":[{"url":"https://{client}.mymedtrics.com","description":"Tenant host; Caddy routes /api-banner/* and /api/* to the bridge (internal only)","variables":{"client":{"default":"","description":"Tenant subdomain"}}},{"url":"http://localhost:8090","description":"local dev (see docker/caddy/Caddyfile for deployed hosts)"}],"security":[{"LegacyToken":[]},{"LegacyBasic":[]}],"components":{"securitySchemes":{"LegacyToken":{"type":"apiKey","in":"header","name":"Authorization","description":"Authorization: Token "},"LegacyBasic":{"type":"http","scheme":"basic"}},"schemas":{"ListEnvelope":{"type":"object","description":"Bridge-wide list envelope. count is always null and page_range always [] (cursor pagination upstream).","properties":{"count":{"type":["integer","null"]},"page_range":{"type":"array"},"per_page":{"type":"integer"},"next":{"type":["string","null"]},"previous":{"type":["string","null"]},"results":{"type":"array"}}},"Sites":{"type":"object","description":"Legacy-shaped banner/sites record as served by the bridge; translated from Connect /sites","properties":{"id":{"type":"integer","description":"legacy id of legacy_id"},"name":{"type":"string","description":"Connect name"},"site_id":{"type":"string","description":"Connect code"},"active":{"type":"string","description":"Connect is_active"},"designate":{"type":"string","description":"Connect is_internal (is_internal_to_designate)"},"student_min":{"type":"string","description":"Connect min_trainees"},"student_max":{"type":"string","description":"Connect max_trainees"},"created_date":{"type":"string","description":"Connect created_at (datetime_to_legacy_iso)"},"updated_date":{"type":"string","description":"Connect updated_at (datetime_to_legacy_iso)"},"description":{"type":"string","description":"literal None"}}}}},"paths":{"/api-banner/sites/":{"get":{"operationId":"sites_list","tags":["Sites"],"parameters":[{"name":"page","in":"query","schema":{"type":"integer"}},{"name":"page_size","in":"query","schema":{"type":"integer","maximum":100}},{"name":"id","in":"query","schema":{"type":"integer"},"description":"maps to Connect legacy_id"},{"name":"name","in":"query","schema":{"type":"integer"},"description":"maps to Connect name"}],"responses":{"200":{"description":"ListEnvelope","content":{"application/json":{"schema":{"allOf":[{"$ref":"#/components/schemas/ListEnvelope"},{"type":"object","properties":{"results":{"type":"array","items":{"$ref":"#/components/schemas/Sites"}}}}]}}}},"400":{"description":"validation error"},"401":{"description":"unauthenticated"},"404":{"description":"not found or out of tenant scope"}}}}}} ``` ## GET /api-banner/sites/{id}/ > ```json {"openapi":"3.1.0","info":{"title":"Medtrics Legacy SIS Bridge (Compatibility API)","version":"draft-2026-10-29"},"servers":[{"url":"https://{client}.mymedtrics.com","description":"Tenant host; Caddy routes /api-banner/* and /api/* to the bridge (internal only)","variables":{"client":{"default":"","description":"Tenant subdomain"}}},{"url":"http://localhost:8090","description":"local dev (see docker/caddy/Caddyfile for deployed hosts)"}],"security":[{"LegacyToken":[]},{"LegacyBasic":[]}],"components":{"securitySchemes":{"LegacyToken":{"type":"apiKey","in":"header","name":"Authorization","description":"Authorization: Token "},"LegacyBasic":{"type":"http","scheme":"basic"}},"schemas":{"Sites":{"type":"object","description":"Legacy-shaped banner/sites record as served by the bridge; translated from Connect /sites","properties":{"id":{"type":"integer","description":"legacy id of legacy_id"},"name":{"type":"string","description":"Connect name"},"site_id":{"type":"string","description":"Connect code"},"active":{"type":"string","description":"Connect is_active"},"designate":{"type":"string","description":"Connect is_internal (is_internal_to_designate)"},"student_min":{"type":"string","description":"Connect min_trainees"},"student_max":{"type":"string","description":"Connect max_trainees"},"created_date":{"type":"string","description":"Connect created_at (datetime_to_legacy_iso)"},"updated_date":{"type":"string","description":"Connect updated_at (datetime_to_legacy_iso)"},"description":{"type":"string","description":"literal None"}}}}},"paths":{"/api-banner/sites/{id}/":{"get":{"operationId":"sites_retrieve","tags":["Sites"],"responses":{"200":{"description":"OK","content":{"application/json":{"schema":{"$ref":"#/components/schemas/Sites"}}}},"400":{"description":"validation error"},"401":{"description":"unauthenticated"},"404":{"description":"not found or out of tenant scope"}}}}}} ``` --- # 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/medtrics-classic-sis-bridge/sites.md?ask=&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.