# Sprinto Cookbooks

### Overview

Sprinto Cookbooks provide ready-to-use API code templates that help you quickly work with the Sprinto Developer API. Each cookbook focuses on a specific use case and is designed to reduce the effort required to write and validate API calls.

Cookbooks are especially useful when you want to understand how queries and mutations are structured and how Sprinto data is returned in real-world scenarios.

***

### What a cookbook contains

Each cookbook includes:

* A complete **query or mutation** definition
* The **expected response structure**
* Context on the fields used and their intended purpose

This format helps you understand how different field types work together and how to adapt the examples for your own integrations.

***

### How to use Sprinto Cookbooks

You can use cookbooks in the following ways:

* **Run directly in the API Playground**\
  Each cookbook includes integrated links to the Sprinto API Playground, allowing you to execute the API call immediately in a browser-based environment.
* **Copy and run in your application**\
  You can copy the query or mutation from a cookbook and execute it using your preferred client library or development framework.

***

### API status

The Sprinto Developer API is currently in beta.

* Endpoints and schema fields may change as new functionality is introduced.
* You should review documentation updates regularly when building production integrations.

***

Cookbooks are intended to help you move faster while learning the Sprinto Developer API. Use them as a starting point and customise the examples to suit your application requirements.


---

# Agent Instructions: 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-cookbooks.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.
