> For the complete documentation index, see [llms.txt](https://docs.enate.net/enate-help/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.enate.net/enate-help/integrations/enate-integrations/apis/api-enums.md).

# API Enums

This document contains a list of values (Integer and String equivalent value) for Enate API enumerations, available as at the July 2026 Feature Wave.

{% file src="/files/PGIHweSoibBqZ7DRhsK5" %}

{% file src="/files/icuPaTQUxhyoQA1YHL57" %}

***

#### Previous feature wave API Enumerations

{% file src="/files/NOMYLdkLOCwPTjDpK80A" %}

Please note that for the 'Status Reasons' method architecturally supports all work items (i.e. Tickets, Cases and Actions), however currently some of them are specific to a Ticket/Case/Action. The specific work Item type that each value is relevant for is noted in the document.

{% hint style="info" %}
Please note that the enum values are not in chronological order, so comparing the JSON enum response to the Swagger model will not be accurate. Please instead refer to this document.
{% endhint %}


---

# 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.enate.net/enate-help/integrations/enate-integrations/apis/api-enums.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.