> For the complete documentation index, see [llms.txt](https://docs.sprinto.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinto.com/api-references/sprinto-api-playground/set-up-api-playground.md).

# Set up API Playground

The Sprinto API Playground is a browser-based GraphQL explorer that lets you interact with the Sprinto Developer API without installing any client libraries or GraphQL tools.

You can use the playground to explore the API schema, test queries and mutations, and validate responses in real time.

The API Playground must be configured each time your browser session expires.

***

### Prerequisites

Before setting up the API Playground, ensure that you have:

* A valid Sprinto account with **administrator privileges**
* A **valid API key** generated from the Sprinto application

For detailed instructions, refer to the guide on generating an API key.

***

### Access the API Playground

Open the API Playground in your preferred web browser based on your data residency region:

* **United States:** Sprinto API Playground
* **Europe:** Sprinto API Playground
* **India:** Sprinto API Playground

***

### Configure the API Playground

Follow these steps to configure the API Playground for your session.

#### Step 1: Open connection settings

From the top bar of the API Playground, click the **Settings** icon to open the **Connection settings** panel.

<figure><img src="/files/2CbAVXvMXc4mBwBhNyyN" alt="" width="563"><figcaption></figcaption></figure>

***

#### Step 2: Add shared headers

In the **Shared headers** section, add the following key–value pairs:

<table><thead><tr><th width="245.44140625">Attribute</th><th width="163.765625">Value</th></tr></thead><tbody><tr><td><code>api-key</code></td><td><code>&#x3C;your API key></code></td></tr><tr><td><code>apollo-require-preflight</code></td><td><code>true</code></td></tr></tbody></table>

These headers authenticate your requests and ensure proper schema loading.

***

#### Step 3: Save the configuration

Click **Save** to apply the changes.

<figure><img src="/files/FB5OBdX5A8W2vkETnEWT" alt="" width="563"><figcaption></figcaption></figure>

***

### Introspect the schema

Once the headers are saved:

* The API automatically introspects the schema, or
* You can manually trigger introspection by clicking **Refetch Schema** from the explorer page

Successful introspection loads the full API schema into the playground.

<figure><img src="/files/VUEk2wIY4j71f1NoZYcL" alt="" width="563"><figcaption></figcaption></figure>

***

### Verify successful setup

After introspection completes, the playground displays the available root types, grouped into:

* **Query**
* **Mutation**

This confirms that the API Playground is correctly configured and ready for use.

<figure><img src="/files/C8hX3HxhWsBRAohZoK6v" alt="" width="563"><figcaption></figcaption></figure>

***

### What you can do next

Once the API Playground is set up, you can:

* Browse available queries and mutations
* Inspect required arguments and response types
* Test paginated queries
* Validate mutations before implementing them in your application

***

### Next steps

After setting up the API Playground, you may want to:

* Make your first API call using the playground
* Review the API structure to understand available operations
* Learn how pagination works for large datasets


---

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

```
GET https://docs.sprinto.com/api-references/sprinto-api-playground/set-up-api-playground.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.
