# APIs

## Intro to Enate APIs

Enate has an API that allows other systems to start, track and interact with work in Enate. Enate APIs communicate via HTTPS Get/Post calls using the JSON data format.

Enate also supports Webhooks, which you can subscribe to so your system is updated on Enate activity in real-time. Check out the Webhooks section for more information:

{% content-ref url="/pages/-MWitakdiScHygZobBO9" %}
[Webhooks](/enate-help/integrations/enate-integrations/webhooks.md)
{% endcontent-ref %}

## Using Application Credentials to access Enate

Enate allows you to create Application Credentials to support multiple concurrent integrations into Enate via APIs. This approach has replaced the need to use standard Enate user accounts for authorized access to the system, which only supported one concurrent access. The Application Credentials records created in User Management section of Builder can be used to generate 'Bearer Tokens' which can be appended in the header of each API to grant access to Enate. Different permission levels can be granted to each Application Credential by selecting from a number of available 'Roles' when creating the Application Credential.

For more information on this, check out the Application Credentials page in the Builder section:

{% content-ref url="/pages/Mb17Q8b06ZFCsOKaKgtN" %}
[Application Credentials](/enate-help/builder/builder-2021.1/user-management/application-credentials.md)
{% endcontent-ref %}

## Swagger - Enate's Interactive API Documentation

If you've got access to an existing Enate environment, you'll be able to access interactive API documentation for Enate’s APIs using your Swagger link, which will be a unique URL specific to your instance available. See the below examples:

**Operational API: <https://yourplatform/operational/swagger>**

**Configuration API: <https://yourplatform/configuration/swagger>**

More general information on Swagger can be found [here](https://swagger.io/docs/specification/v3_0/about/).

![](/files/-MXlcVYbs_aqVocOqjGg)

## Sample Integration Patterns Using Enate's API's

{% content-ref url="/pages/-MfY7fKX1YUUX8c7NMnz" %}
[Create a Webform that turns requests into Tickets with Enate's APIs](/enate-help/integrations/enate-integrations/api-sample-webform-front-end-to-post-tickets.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://docs.enate.net/enate-help/integrations/enate-integrations/apis.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.