> For the complete documentation index, see [llms.txt](https://docs.adsecure.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adsecure.com/docs/graphql/overview.md).

# Overview

Here are some quick links to get you up and running with the GraphQL API:

* [Authentication](/docs/graphql/forming-calls.md#authentication)
* [Root endpoint](/docs/graphql/forming-calls.md#the-graphql-endpoint)
* [Rate limits](#!)

## What is GraphQL?

The [GraphQL](https://graphql.org/) data query language is:

* **A** [**specification**](https://spec.graphql.org/). The spec determines the validity of the schema on the API server. The schema determines the validity of client calls.
* **Strongly typed**. The schema defines an API's type system and all object relationships.
* [**Introspective**](/docs/graphql/forming-calls.md#discovering-the-graphql-api). A client can query the schema for details about the schema.
* [**Hierarchical**](/docs/graphql/forming-calls.md#communicating-with-graphql). The shape of a GraphQL call mirrors the shape of the JSON data it returns. Nested fields let you query for and receive only the data you specify in a single round trip.
* **An application layer**. GraphQL is not a storage model or a database query language. The graph refers to graph structures defined in the schema, where nodes define objects and edges define relationships between objects. The API traverses and returns application data based on the schema definitions, independent of how the data is stored.

## Why is AdSecure using GraphQL?

AdSecure chose GraphQL for our API because it offers significantly more flexibility for our integrators. The ability to define precisely the data you want—and only the data you want—is a powerful advantage over a REST API. GraphQL lets you replace multiple REST requests with a single call to fetch the data you specify.


---

# 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.adsecure.com/docs/graphql/overview.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.