Merge pull request #815 from netwrix/jean-perez/changetracker-api-reference feat(changetracker): add interactive API reference for Hub 8.1

docs/changetracker/8.1/integration/api/api-reference.mdx

@@ -0,0 +1,16 @@
+---
+title: API Reference
+description: Interactive reference for all ChangeTracker Hub API endpoints
+sidebar_position: 25
+---
+
+import BrowserOnly from '@docusaurus/BrowserOnly';
+
+<BrowserOnly>
+  {() => {
+    window.location.replace('/docs/changetracker/8_1/integration/api/reference');
+    return null;
+  }}
+</BrowserOnly>
+
+Redirecting to the [ChangeTracker Hub API Reference](/docs/changetracker/8_1/integration/api/reference)…

docs/changetracker/8.1/integration/api/overview.md

@@ -12,15 +12,21 @@ Netwrix Change Tracker provides a comprehensive REST API that allows customers t
 
 All API endpoints require authentication. See [Authentication](/docs/changetracker/8.1/integration/api/authentication.md) for an example script.
 
+## API Reference
+
+For a complete interactive reference of all Netwrix Change Tracker Hub API endpoints, see the [Netwrix Change Tracker Hub API Reference](/docs/changetracker/8_1/integration/api/reference). The Netwrix Change Tracker Hub (the central management server) generates this reference directly from its OpenAPI 3.0 spec, covering all available endpoints with request/response schemas.
+
+The raw OpenAPI 3.0 spec (YAML) is also [available for download](/openapi/changetracker-hub-8.1.yaml).
+
 ## Available Endpoints
 
 The following API endpoints are available in Netwrix Change Tracker:
 
-- [Agents](/docs/changetracker/8.1/integration/api/agents.md) – Pull data on agent statuses, configurations, and group memberships using the agentsRanked endpoint. This API allows you to retrieve detailed information about all agents in your environment, including their group memberships and applied tracking templates.
+- [Agents](/docs/changetracker/8.1/integration/api/agents.md) – Pull data on agent statuses, configurations, and group memberships using the agentsRanked endpoint. Use this API to retrieve detailed information about all agents in your environment, including their group memberships and applied tracking templates.
 
-- [Register Agents](/docs/changetracker/8.1/integration/api/register-agents.md) – Normally used by agents to register with the Hub, but this API allows you to register proxied devices to be accessed through a proxy agent.
+- [Register Agents](/docs/changetracker/8.1/integration/api/register-agents.md) – Agents normally use this API to register with the Hub, but you can also use it to register proxied devices accessed through a proxy agent.
 
-- [Credentials](/docs/changetracker/8.1/integration/api/credentials.md) – Manage authentication credentials used by ChangeTracker to connect to various systems and services. This API provides endpoints for creating, retrieving, updating, and deleting credentials for different credential types including Shell, Database, FTP, Cloud, ESX, ITSM, and Splunk.
+- [Credentials](/docs/changetracker/8.1/integration/api/credentials.md) – Manage authentication credentials that ChangeTracker uses to connect to various systems and services. This API provides endpoints for creating, retrieving, updating, and deleting credentials for different credential types including Shell, Database, FTP, Cloud, ESX, ITSM, and Splunk.
 
 ## API Usage Best Practices
 
@@ -38,7 +44,7 @@ When working with the ChangeTracker API, consider the following best practices:
 
 ## Example Usage
 
-Below is a simple example of how to use the API with PowerShell:
+The following example shows how to use the API with PowerShell:
 
 ```powershell
 # Set up a session variable for the Admin user
@@ -64,4 +70,4 @@ $requestBody = @{
 $result = Invoke-RestMethod -Method Post -ContentType application/json -Uri $uri -WebSession $myWebSession -Body $requestBody
 ```
 
-For more detailed information about each API endpoint, please refer to the specific API documentation pages linked above.
+See the [Available Endpoints](#available-endpoints) section for documentation pages covering each API endpoint.