Skip to content

Commit f14b22e

Browse files
authored
fix: fix link to GET Schemas API in enable-app.md (#370)
1 parent 4b064b1 commit f14b22e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

docs/tutorials/1.developers/4.apps-development/3.enable-app.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ You can use the DIAL API to create a schema-rich application of a specific type.
5252
Send a [PUT](https://dialx.ai/dial_api#tag/Applications/operation/saveCustomApplication) request to DIAL Core, where you provide:
5353

5454
- Standard parameters for the application (`displayName`, `description` etc.). Refer to [dynamic setting of DIAL Core](https://github.com/epam/ai-dial-core?tab=readme-ov-file#dynamic-settings) to see all the supported parameters for applications.
55-
- `applicationTypeSchemaId`: The identifier of the schema for the application type you want to use as a template. You can retrieve available schemas via the [GET Schemas](https://rail-landing.staging.deltixhub.io/dial_api#tag/Applications/operation/listCustomApplicationSchemas) API call.
55+
- `applicationTypeSchemaId`: The identifier of the schema for the application type you want to use as a template. You can retrieve available schemas via the [GET Schemas](https://dialx.ai/dial_api#tag/Applications/operation/listCustomApplicationSchemas) API call.
5656
- `applicationProperties`: A valid JSON object representing the application's structure, conforming to the specified schema. If the JSON object is invalid, the request will fail.
5757

5858
- If `applicationTypeSchemaId` is absent or `NULL`, `applicationProperties` are not required. If `applicationTypeSchemaId` is not provided, then this is not a schema-rich application.
@@ -299,4 +299,4 @@ You can create schema-rich application types with custom UIs to replace the defa
299299

300300
##### Application Endpoint
301301

302-
To enable DIAL apps to communicate with your application, you can register your application's endpoint in DIAL Core as a `route`. You can apply roles, usage limits, and associate API keys with these routes, enabling seamless integration with DIAL Core features. For details on registering routes, refer to [DIAL Core dynamic settings](https://github.com/epam/ai-dial-core?tab=readme-ov-file#dynamic-settings).
302+
To enable DIAL apps to communicate with your application, you can register your application's endpoint in DIAL Core as a `route`. You can apply roles, usage limits, and associate API keys with these routes, enabling seamless integration with DIAL Core features. For details on registering routes, refer to [DIAL Core dynamic settings](https://github.com/epam/ai-dial-core?tab=readme-ov-file#dynamic-settings).

0 commit comments

Comments
 (0)