# Body Parameters

### GraphQL

GraphQL is a type of query language and server-side runtime for APIs. It prioritizes giving clients exactly the data they request and no more, making APIs fast, flexible, and developer friendly. Is not tied to any specific database or storage engine and is backed by existing code and data. 

<figure><img src="/files/Ev826UVCHBG6YJ4tFN56" alt=""><figcaption></figcaption></figure>

#### Body:

* *Input Field Type:* Text Field
* *Description:* This field allows the user to specify a unique name for the Custom API.
* *Usage:* Enter a concise and descriptive name that succinctly identifies the API within the system. This name should facilitate easy recognition and differentiation among multiple APIs.

  <figure><img src="/files/DRSs1kVHXrtd4V5U3vi9" alt=""><figcaption></figcaption></figure>

#### Parameter Name:

* *Input Field Type:* Text Field
* *Description:* This field allows the user to define a unique name for the Custom API.
* *Usage:* Enter a concise and descriptive name that succinctly identifies the API within the system. This name should facilitate easy recognition and differentiation among multiple APIs.

  <figure><img src="/files/TbctGjyhGw1rP4EXovxq" alt=""><figcaption></figcaption></figure>

#### Value:

* *Input Field Type:* Text Field
* *Description:* This field allows the user to specify a unique name for the Custom API.
* *Usage:* Enter a concise and descriptive name that succinctly identifies the API within the system. This name should facilitate easy recognition and differentiation among multiple APIs.

  <figure><img src="/files/vznFW0sCUJGMWfchWbst" alt=""><figcaption></figcaption></figure>

#### Description:

* *Input Field Type:* Text Field
* *Description:* This field allows the user to specify a unique name for the Custom API.
* *Usage:* Enter a concise and descriptive name that succinctly identifies the API within the system. This name should facilitate easy recognition and differentiation among multiple APIs.

  <figure><img src="/files/Spu2zLh1v41Gbzv8c0vw" alt=""><figcaption></figcaption></figure>

#### Required:

* *Input Field Type:* Check Box&#x20;
* *Description:* This field allows the user to specify a unique name for the Custom API.
* *Usage:* Enter a concise and descriptive name that succinctly identifies the API within the system. This name should facilitate easy recognition and differentiation among multiple APIs.

  <figure><img src="/files/iaYFKMKoAnJPD6WGRNMf" alt=""><figcaption></figcaption></figure>

***

### JSON&#x20;

<figure><img src="/files/3MEA7C5ylzSnyFV598kW" alt=""><figcaption></figcaption></figure>

#### Body:

* *Input Field Type:* Text Field
* *Description:* This field allows the user to specify a unique name for the Custom API.
* *Usage:* Enter a concise and descriptive name that succinctly identifies the API within the system. This name should facilitate easy recognition and differentiation among multiple APIs.

  <figure><img src="/files/ykKej2tu9sepiAtvjOdA" alt=""><figcaption></figcaption></figure>

#### Parameter Name:

* *Input Field Type:* Text Field
* *Description:* This field allows the user to specify a unique name for the Custom API.
* *Usage:* Enter a concise and descriptive name that succinctly identifies the API within the system. This name should facilitate easy recognition and differentiation among multiple APIs.

  <figure><img src="/files/Q5sAPZ9bxq9OzpAcQbWr" alt=""><figcaption></figcaption></figure>

#### Value:

* *Input Field Type:* Text Field
* *Description:* This field allows the user to specify a unique name for the Custom API.
* *Usage:* Enter a concise and descriptive name that succinctly identifies the API within the system. This name should facilitate easy recognition and differentiation among multiple APIs.

  <figure><img src="/files/Rbuay4OMQY6pDILoN6p1" alt=""><figcaption></figcaption></figure>

#### Description:

* *Input Field Type:* Text Field
* *Description:* This field allows the user to specify a unique name for the Custom API.
* *Usage:* Enter a concise and descriptive name that succinctly identifies the API within the system. This name should facilitate easy recognition and differentiation among multiple APIs.

  <figure><img src="/files/xLfEttCdGu9WuVliGZxG" alt=""><figcaption></figcaption></figure>

  #### Required:

  * *Input Field Type:* Check Box&#x20;
  * *Description:* This field allows the user to specify a unique name for the Custom API.
  * *Usage:* Enter a concise and descriptive name that succinctly identifies the API within the system. This name should facilitate easy recognition and differentiation among multiple APIs.

    <figure><img src="/files/mh6WNXSOHtVK11idkIfM" alt=""><figcaption></figcaption></figure>


---

# 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.aicrisk.com/admin/custom-apis/adding-a-new-api/body-parameters.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.