> For the complete documentation index, see [llms.txt](https://docs.mdintegrations.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.mdintegrations.com/partner/troubleshooting/technical-concepts.md). # Technical Concepts Technical Concepts is where the mechanics of the MDI API are explained in depth — the parts of the system worth understanding once, up front, rather than re-deriving from the reference docs every time you touch a new endpoint. It walks through how authentication works from first token request to ongoing refresh, the conventions every request and response follows regardless of endpoint, and how to interpret and handle the errors the API sends back, alongside related foundations like webhooks and compliance that shape how you build against the platform. Think of it as the conceptual companion to the Full API Reference: the reference tells you what each endpoint does, while this subsection explains the patterns that hold across all of them, so you only have to learn each one once. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.mdintegrations.com/partner/troubleshooting/technical-concepts.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.