# API

{% hint style="success" %}

#### Like what your seeing?

Support us as a [GitHub Sponsor](/old-kb/where-to-buy/become-a-sponsor.md) and get instant access to all our assets, exclusive tools and assets, escalated support and issue tracking and our gratitude.\
\
These articles are made possible by our [GitHub Sponsors](/old-kb/where-to-buy/become-a-sponsor.md) ... become a sponsor today!
{% endhint %}

## Introduction

The UX API provides low level access to all of Heathen UX's features. API's members are all static classes and are used by higher level game object componenets to deliver the funcitonality of Heathen's UX. The UX API can be used to access features and funcitons of UX without the need of a GameObject reference and can be used to create tailor made systems and managers for your projects.

## Features

### Simple yet powerful

Clean simple, approchable static methods make most tasks a 1 liner

```csharp
API.Cursors.SetState(state);
```

```csharp
API.Windows.Focused.Maximize();
```

```csharp
API.Log.SaveToTextFile(fileName);
```

### Unity Native

Heathen's APIs are built with the Unity developer and programmer in mind. We make use of UnityEvents, Actions, ScriptableObjects and other standard Unity concepts and styles throughout the API. 

Where nessisary the Heathen API handles the various options in Unity, for example API.Cursors and API.Windows is comptable with both the old and new Unity Input systems and automatically uses the appropreate option.


---

# 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://kb.heathen.group/old-kb/toolkit-for-ui-and-ux/unity/api.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.