> 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](https://docs.durohub.com/rate-limits/rate-limits.md) for stability
* One evolving schema. Most retirements are marked `@deprecated` first; a breaking change is noted on the affected page and in the [changelog](https://next.durohub.com/changelog)

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

* [Apollo Explorer](https://api.durohub.com/graphql)

{% hint style="info" %}
`https://api.durohub.com/graphql` is a single **composed schema**: Duro federates multiple internal services (components, change orders, sourcing, and more) into one supergraph behind this one endpoint. You never talk to the individual services — everything documented on this site is queried through this URL, and Apollo Explorer there always reflects the full, current contract.

Using the EU or GovCloud region? Use your region's host — see [Endpoints](https://docs.durohub.com/readme.md#endpoints).
{% endhint %}

* [Apollo Client](https://www.apollographql.com/docs/react/)
* [Postman](https://www.postman.com/) (with GraphQL support)

### Next Steps

Learn how to [authenticate your requests](https://docs.durohub.com/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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.durohub.com/getting-started/introduction.md?ask=<question>&goal=<user_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.
