# Description

The **PRIZM API** allows interaction with PRIZM nodes using HTTP requests to port 9976. Most HTTP requests can use either the GET or POST methods, but some API calls accept only the POST method for security reasons. Responses are returned as JSON objects.

### Each API call is documented below, with definitions given for HTTP request parameters and JSON response fields, followed by an example:

{% hint style="info" %}

* The JSON response fields are each followed by one of S for *string*, A for *array*, O for *object*, N for *number* or B for *boolean*.
* In the examples, the PRIZM node is represented as localhost and requests and responses are formatted for easy reading; line breaks and spaces are not actually used except in some parameter values. All requests are in URL format which implies the HTTP GET method. When GET is allowed, the URL can be entered into a browser URL field but proper URL encoding is usually required (e.g., spaces in a parameter value must be replaced by + or %20). Otherwise, the URL should be used as a guide to preparing an HTTP POST request using cURL, for example.
  {% endhint %}

All API calls can be viewed and tested at [**http://localhost:9976/test**](http://localhost:9976/test) while the local server node is running. For specific API calls, use [**http://localhost:9976/test?requestType=**](http://localhost:9976/test?requestType=)***specificRequestType.***

{% content-ref url="/pages/-MSL8SLi0rh-BUXAykLv" %}
[Prizm API](/pzm/prizm-api.md)
{% endcontent-ref %}

{% content-ref url="/pages/-MSVDctTIKX71Yb3TnYT" %}
[Prizm API Examples](/pzm/prizm-api/prizm-api-examples.md)
{% endcontent-ref %}


---

# 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://prizm.gitbook.io/pzm/prizm-api/description.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.