> For the complete documentation index, see [llms.txt](https://docs.padprotocol.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.padprotocol.org/api_desc.md).

# API Description

***

This session describes endpoints of the PAD API. The endpoints may appear in subsessions more than once as they are titled by a role of PAD. A description of an endpoint consists of its method, URI, request parameters and response statuses, with examples.

## Base URL and version

Base URL: <https://api.pad.tech>

The only version available now is `v0`. To access the URI `/trustees`, for example, the URL will be <https://api.pad.tech/v0/trustees>.

## Types

"Primitive" types are written in lowercase. Examples:

* integer
* number
* string
* object (JSON object)
* array
* dict (dictionary/key-value pair where values have the same type)
* enum

Arrays are written in the form array\<T> which indicates it is an array where items are all in type T.

Dictionaries are written in the form dict\<KeyT, ValueT> which indicates it is an object where the keys are in type KeyT and the values are in type ValueT.

Stringified objects are written like string\<T>. A string of this type should be able to parse as an object of type T.

Defined types are capitalised. Examples:

* Encryption
* Token
* TrusteeId
* DataRequest


---

# 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.padprotocol.org/api_desc.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.