🤖 Auto-merge documentation from branches

docs.json

@@ -1677,18 +1677,30 @@
                       "nightly/tyk-apis",
                       {
                         "group": "Gateway",
+                        "pages": [
+                          "nightly/tyk-gateway-api"
+                        ],
                         "openapi": "swagger/nightly/gateway-swagger.yml"
                       },
                       {
                         "group": "Dashboard",
+                        "pages": [
+                          "nightly/tyk-dashboard-api"
+                        ],
                         "openapi": "swagger/nightly/dashboard-swagger.yml"
                       },
                       {
                         "group": "Dashboard Admin",
+                        "pages": [
+                          "nightly/dashboard-admin-api"
+                        ],
                         "openapi": "swagger/nightly/dashboard-admin-swagger.yml"
                       },
                       {
                         "group": "MDCB",
+                        "pages": [
+                          "nightly/tyk-mdcb-api"
+                        ],
                         "openapi": "swagger/nightly/mdcb-swagger.yml"
                       },
                       "nightly/tyk-identity-broker/tib-rest-api"
@@ -1823,6 +1835,9 @@
                   "nightly/product-stack/tyk-enterprise-developer-portal/deploy/configuration",
                   {
                     "group": "Developer Portal API",
+                    "pages": [
+                      "nightly/product-stack/tyk-enterprise-developer-portal/api-documentation/tyk-edp-api"
+                    ],
                     "openapi": "swagger/nightly/enterprise-developer-portal-swagger.yaml"
                   },
                   "nightly/product-stack/tyk-enterprise-developer-portal/api-documentation/list-of-endpoints/portal-api-list-of-endpoints",
@@ -1974,6 +1989,9 @@
                       "nightly/ai-management/ai-studio/notifications",
                       {
                         "group": "API Documentation",
+                        "pages": [
+                          "nightly/ai-management/ai-studio/ai-studio-swagger"
+                        ],
                         "openapi": "swagger/nightly/ai-studio-swagger.yml"
                       }
                     ]

nightly/ai-management/ai-studio/ai-studio-swagger.mdx

@@ -2,7 +2,8 @@
 title: "Tyk AI Studio API"
 description: "Tyk AI Studio API"
 keywords: "OpenAPI Spec for AI Studio, Tyk AI Studio OAS, Tyk AI Portal REST"
-sidebarTitle: "API Documentation"
+sidebarTitle: "Overview"
 canonical: "https://tyk.io/docs/ai-management/ai-studio/ai-studio-swagger"
 ---
 
+This is the API for the AI Studio user and group management system.

nightly/dashboard-admin-api.mdx

@@ -1,7 +1,20 @@
 ---
 title: "Tyk Dashboard Admin API"
+description: "Tyk Dashboard Admin API documentation. This page provides details on how to use the Tyk Dashboard Admin API for setting up and provisioning a Tyk Dashboard instance."
 order: 4
-sidebarTitle: "Dashboard Admin"
+sidebarTitle: "Overview"
 canonical: "https://tyk.io/docs/dashboard-admin-api"
 ---
 
+<img src="https://tyk.io/docs/img/dashboard_admin_swagger_image.png" width="963" height="250"/>
+
+For Tyk On-Premises installations only, the Dashboard Admin API has two endpoints and is used to set up and provision a Tyk Dashboard instance without the command line.
+
+In order to use the Dashboard Admin API, you'll need to get the `admin_secret` value from your Tyk Dashboard configurations.
+
+The secret you set should then be sent along as a header with each Dashboard Admin API Request in order for it to be successful:
+
+```
+admin-auth: <your-secret>
+```
+

nightly/product-stack/tyk-enterprise-developer-portal/api-documentation/tyk-edp-api.mdx

@@ -1,7 +1,23 @@
 ---
-title: "Tyk Enterprise Developer Portal API"
+title: "Tyk Developer Portal API"
+description: "Tyk Developer Portal API documentation. This page provides details on how to use the Tyk Developer Portal Management API for managing portal resources."
 order: 3
-sidebarTitle: "Developer Portal API"
+sidebarTitle: "Overview"
 canonical: "https://tyk.io/docs/product-stack/tyk-enterprise-developer-portal/api-documentation/tyk-edp-api"
 ---
 
+<img src="https://tyk.io/docs/img/developer_portal_swagger_image.png" width="963" height="250"/>
+
+## <a name="introduction"></a> Introduction
+
+The Tyk Developer Portal Management API offers programmatic
+access to all portal resources that your instance of the portal manages.
+This API repeats functionality of the user interface and enables APIs
+consumers integrating their portal instances with their other IT systems
+such as billings, CRMs, ITSM systems and other software.
+
+
+## Authentication
+
+This API requires an admin authorisation token that is available for admin
+users of the portal in the profile page.

nightly/tyk-dashboard-api.mdx

@@ -1,7 +1,37 @@
 ---
 title: "Tyk Dashboard API"
+description: "Tyk Dashboard API documentation. This page provides details on how to use the Tyk Dashboard API for managing organisations, users, API definitions, and more."
 order: 3
-sidebarTitle: "Dashboard"
+sidebarTitle: "Overview"
 canonical: "https://tyk.io/docs/tyk-dashboard-api"
 ---
 
+<img src="https://tyk.io/docs/img/swagger_dashboard_image.png" width="963" height="250"/>
+
+## <a name="introduction"></a> Introduction
+
+The Tyk Dashboard API offers granular, programmatic access to a centralised database of resources that your Tyk nodes can pull from. This API has a dynamic user administrative structure which means the secret key that is used to communicate with your Tyk nodes can be kept secret and access to the wider management functions can be handled on a user-by-user and organisation-by-organisation basis.
+
+A common question around using a database-backed configuration is how to programmatically add API definitions to your Tyk nodes, the Dashboard API allows much more fine-grained, secure and multi-user access to your Tyk cluster, and should be used to manage a database-backed Tyk node.
+
+The Tyk Dashboard API works seamlessly with the Tyk Dashboard (and the two come bundled together).
+
+## <a name="security-hierarchy"></a> Security Hierarchy
+
+The Dashboard API provides a more structured security layer to managing Tyk nodes.
+
+### Organisations, APIs and Users
+
+With the Dashboard API and a database-backed Tyk setup, (and to an extent with file-based API setups - if diligence is used in naming and creating definitions), the following security model is applied to the management of Upstream APIs:
+
+* **Organisations**: All APIs are *owned* by an organisation, this is designated by the 'OrgID' parameter in the API Definition.
+* **Users**: All users created in the Dashboard belong to an organisation (unless an exception is made for super-administrative access).
+* **APIs**: All APIs belong to an Organisation and only Users that belong to that organisation can see the analytics for those APIs and manage their configurations.
+* **API Keys**: API Keys are designated by organisation, this means an API key that has full access rights will not be allowed to access the APIs of another organisation on the same system, but can have full access to all APIs within the organisation.
+* **Access Rights**: Access rights are stored with the key, this enables a key to give access to multiple APIs, this is defined by the session object in the core Tyk API.
+
+In order to use the Dashboard API, you'll need to get the 'Tyk Dashboard API Access Credentials' secret from your user profile on the Dashboard UI.
+
+The secret you set should then be sent along as a header with each Dashboard API Request in order for it to be successful:
+
+`authorization: <your-secret>`

nightly/tyk-gateway-api.mdx

@@ -1,8 +1,32 @@
 ---
 title: "Tyk Gateway API"
+description: "Tyk Gateway API documentation. This page provides details on how to use the Tyk Gateway API for managing session objects, policies, API definitions, and more."
 keywords: "OpenAPI Spec, OpenAPI Specification, OAS, REST, Tyk Gateway OpenAPI Spec, Tyk Gateway OAS, API Gateway OAS, API Gateway REST"
 order: 3
-sidebarTitle: "Gateway"
+sidebarTitle: "Overview"
 canonical: "https://tyk.io/docs/tyk-gateway-api"
 ---
 
+<img src="https://tyk.io/docs/img/swagger_gateway_image.png" width="963" height="250"/>
+<img src="https://tyk.io/docs/img/swagger_gateway_direction_image.png" width="946" height="392"/>
+
+The Tyk Gateway API is the primary means for integrating your application with the Tyk API Gateway system. This API is very small, and has no granular permissions system. It is intended to be used purely for internal automation and integration.
+
+**Warning: Under no circumstances should outside parties be granted access to this API.**
+
+The Tyk Gateway API is capable of:
+
+* Managing session objects (key generation).
+* Managing and listing policies.
+* Managing and listing API Definitions (only when not using the Tyk Dashboard).
+* Hot reloads / reloading a cluster configuration.
+* OAuth client creation (only when not using the Tyk Dashboard).
+
+In order to use the Gateway API, you'll need to set the **secret** parameter in your tyk.conf file.
+
+The shared secret you set should then be sent along as a header with each Gateway API Request in order for it to be successful:
+
+`x-tyk-authorization: <your-secret>`
+<br/>
+
+<b>The Tyk Gateway API is subsumed by the Tyk Dashboard API in Pro installations.</b>

nightly/tyk-mdcb-api.mdx

@@ -1,8 +1,12 @@
 ---
 title: "Tyk MDCB API"
+description: "Tyk MDCB API documentation. This page provides details on how to use the Tyk Multi Data Center Bridge (MDCB) API for monitoring connected Data Planes and accessing diagnostic data."
 keywords: "OpenAPI Spec, OpenAPI Specification, OAS, REST, Tyk MDCB OpenAPI Spec, Tyk MDCB OAS, MDCB API REST"
 order: 3
-sidebarTitle: "Multi Data Center Bridge"
+sidebarTitle: "Overview"
 canonical: "https://tyk.io/docs/tyk-mdcb-api"
 ---
 
+This API provides operations for monitoring Data Planes connected to MDCB and accessing diagnostic data. 
+It includes endpoints for retrieving connected data plane details, performing health checks, 
+and accessing Go's built-in pprof diagnostics for advanced performance profiling.