> For the complete documentation index, see [llms.txt](https://docs.akto.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.akto.io/api-inventory/concepts/data-types.md).

# Data Types

## What is Data Type?

**`Data Type`** refers to the specific formats or structures used to represent different types of data in requests and responses. Simply put, data types are like labels that tell you what kind of information you're dealing with in APIs. For example:

* EMAIL
* JWT
* ADDRESS
* IP\_ADDRESS
* PHONE\_NUMBER

## Customize Data Type

Akto comes with over 40 built-in data types by default. However, some businesses might have unique data types, such as a transaction ID prefixed with "TXN\_ID". These are specific to your business. If you want Akto to recognize these data types, you can configure them in the application.

If you have a highly sensitive, non-standard data type, you can define the pattern in Akto. Afterward, Akto will inform you about which API is sharing this data. For more information on creating custom data type, please refer to this documentation-[ Create a Custom Data Type](https://docs.akto.io/api-inventory/how-to/create-a-custom-data-type)


---

# 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, and the optional `goal` query parameter:

```
GET https://docs.akto.io/api-inventory/concepts/data-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.