> For the complete documentation index, see [llms.txt](https://docs.labii.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.labii.com/widgets/column-widgets/integration/api.md). # API Labii’s API Type Integration enables seamless connectivity with external APIs to automatically update other columns in Labii based on retrieved data. ## Overview Labii’s API Type Integration enables seamless connectivity with external APIs to automatically update other columns in Labii based on retrieved data. By configuring an API endpoint, request parameters, and response mapping, users can trigger API calls to fetch relevant information and populate multiple fields within a record. This integration is particularly useful for synchronizing external databases, enriching records with third-party data, or automating workflows such as pulling experiment details, updating statuses, or retrieving analytics. It enhances efficiency by reducing manual data entry and ensuring real-time accuracy across connected systems. ## Widgets * [API](/widgets/column-widgets/integration/api/api.md) - The Labii API widget is a powerful tool that allows users to seamlessly connect to various APIs and execute API calls with ease. --- # 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.labii.com/widgets/column-widgets/integration/api.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.