> For the complete documentation index, see [llms.txt](https://docs.durohub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.durohub.com/getting-started/introduction.md). # Introduction The Duro GraphQL API provides a powerful interface to interact with your product lifecycle management data. This guide will help you understand the core concepts and get started with integration. ### Why GraphQL? Our API is built using GraphQL, offering several advantages: * Request exactly the data you need and ability to fetch multiple resources in parallel * Strong typing and schema validation * Efficient data loading * Interactive documentation and exploration ### API Architecture The Duro API follows these core principles: * RESTful-like resource patterns * Clear name-spaced resources * Consistent error handling * Rate limiting for stability * Versioned schema updates ### Prerequisites Before you begin, you'll need: * A Duro account * Basic understanding of GraphQL * Your preferred GraphQL client ### Tools and SDKs We recommend using these tools: * [GraphQL Playground](https://api.durohub.com/graphql) * [Apollo Client](https://www.apollographql.com/docs/react/) * [Postman](https://www.postman.com/) (with GraphQL support) ### Next Steps Learn how to [authenticate your requests](/getting-started/authentication.md) to get started. --- # 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.durohub.com/getting-started/introduction.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.