> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-pulse/endpoints.md).

# Endpoints

Endpoints for which the health check will be performed based on the configured interval.

### Endpoints

1. Navigate to **`IZ Pulse`** -> **`Endpoints`** 
2. Each endpoint can have multiple versions
3. Click on the **`Add Version`** action to create a new endpoint version. Refer Configure Endpoint

### Versions

1. Navigate to **`IZ Pulse`** -> **`Endpoints`** and click on the **`Plus`** icon to view all the versions <br>

   <figure><img src="https://1912836914-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F9vAxMuDrkUkB4OXlH9CL%2Fuploads%2Fu63lbE3JxRBw8W4ggpdQ%2Fendpoint-versions.png?alt=media&amp;token=275a2964-6187-429b-a5f4-cb7ef314545f" alt=""><figcaption></figcaption></figure>
2. Details include:
   1. **`Endpoint`** - Endpoint for which the health check should be performed
   2. **`Method`** - HTTP method of the endpoint Eg: GET, POST etc
   3. **`Version`** - Version of the endpoint
   4. **`Status`** - Active or Disabled
   5. **`Visibility`** - Private or Public. Private endpoints will not be visible in Public Status Pages
   6. **`Health`** - Health of the endpoint. Health will be available once the **`Health Check`** job schedule is configured
3. Click on **`Edit Endpoint`** action to edit the endpoint details

### See Also

* [Configure Schedule](/product-guides/integral-zone/iz-suite/iz-pulse/configure-schedule.md)
* [Categories](/product-guides/integral-zone/iz-suite/iz-pulse/categories.md)
* [Status Pages](/product-guides/integral-zone/iz-suite/iz-pulse/status-pages.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/iz-pulse/endpoints.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.