> 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/development/quickstart.md).

# Quickstart

Get up and running with our API and start developing your AdSecure integration.

Integrating AdSecure into your app can begin as soon as you create a AdSecure account, requiring only 2 steps:

* [Obtain your API key](#obtain-your-api-key) so AdSecure can authenticate your integration’s API requests.
* [Make a test API request](#make-a-test-api-request) to confirm everything is up and running.

## Obtain your API key

AdSecure authenticates your API requests using your account’s API key. If you do not include your key when making an API request, or use one that is incorrect or outdated, AdSecure returns an error.

Every account is provided with an API key. You can generate your own key by accessing your profile - [API integrations](https://app.adsecure.com/settings/api-integrations). Some additional ones can be created by contacting your account manager. In our code examples, we include randomly generated API keys. Replace these with your own to see code examples being executed successfully.

If you don't have an account, please sign up for an account here(<https://app.adsecure.com/auth/signup>).

## Make a test API request

To check that your integration is working correctly, make a test API request using your secret key to retrieve your [`User`](/api/graphql/user.md)'s details.

```bash
curl -H 'x-api-key: nhwQ4taIgNciu3xrabY8BMFXAZGyYGtc8r' -d '
{
  "query":"query { viewer { user { name }}}"
}' -X POST https://api.adsecure.com/graphql
```

AdSecure returns a [`User`](/api/graphql/user.md) object in response to your API request.

```json
{
  "data": {
    "viewer": {
      "user": {
        "name": "Your user's name!"
      }
    }
  }
}
```

Once you have successfully made an API request, you’re ready to begin integrating AdSecure.

#### Notes

For the rest of the documentation, we will show these cURL examples using a shorthand format that leaves out all the bits that are the same in every request, like the hostname, port, headers, and the cURL command itself. Instead of showing a full request like:

```bash
curl -H 'x-api-key: nhwQ4taIgNciu3xrabY8BMFXAZGyYGtc8r' -d '
{
  "query":"query { viewer { user { name }}}"
}' -X POST https://api.adsecure.com/graphql
```

We will show it in this shorthand format:

```bash
query {
  viewer {
    user {
      name
    }
  }
}
```

In fact, this format is the one used to represents a [GraphQL](https://graphql.org/) query. If you're not familiar with GraphQL, please have a look to at its [dedicated section](/docs/graphql/overview.md) in this documentation.


---

# 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/development/quickstart.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.