> For the complete documentation index, see [llms.txt](https://ed.sunbird.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ed.sunbird.org/use/source-code/manage-learn/ml-report-service/apis.md). # API's The ML Report Service Postman Collection is a comprehensive resource for interacting with the ML Report Service. It includes organized endpoints, detailed documentation, and example workflows, providing a valuable reference for developers. Leverage this collection to enhance productivity and collaboration in ML Services. #### Public APIs Public APIs are accessible gateways for apps and portals to access external resources. They require a public URL and user authentication. The provided Postman collection simplifies API interactions for developers. [Public Postman collection](https://documenter.getpostman.com/view/7997930/2s946chuaT#198edf86-1031-41a5-bf51-1c7074638e79) {% embed url="" %} #### Private APIs Private APIs facilitate the creation of resources and programs, necessitating authorization and user authentication tokens, as well as a private IP, to access the APIs securely. [Private APIs Postman collection](https://documenter.getpostman.com/view/7997930/2s946chuaT#d565c37e-1714-48cd-86a9-b47753469312) {% embed url="" %} --- # 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://ed.sunbird.org/use/source-code/manage-learn/ml-report-service/apis.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.