# API documentation

- [How to write incredible API documentation](https://gitbook.com/docs/guides/api-documentation/how-to-write-incredible-api-documentation.md): What we’ve learned about writing API docs that drive adoption and reduce support.
- [Document your API in GitBook in 5 simple steps](https://gitbook.com/docs/guides/api-documentation/document-your-api-in-gitbook-in-5-simple-steps.md): Learn how to build beautiful, interactive API documentation in GitBook.
- [API docs: The seven principles of great API docs and how to apply them](https://gitbook.com/docs/guides/api-documentation/api-documentation-principles.md): Create great API documentation for your users using these foundational principles


---

# Agent Instructions: 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:

```
GET https://gitbook.com/docs/guides/api-documentation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
