Skip to content
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions en/docs/api-design-manage/design/design-api-overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,7 @@ Additionally, you can also convert existing SOAP services or backends to REST AP

**Create an API based on a Service**

You can create services and publish it to WSO2 API Manager, such as you can create an integration service using WSO2 Integration Studio or a streaming integration service using the Streaming Integration Tooling. Refer to the [documentation on Creating an API Using a Service]({{base_path}}/api-design-manage/design/create-api/create-an-api-using-a-service).
You can create services and publish them to WSO2 API Manager. For example, you can create an integration service using WSO2 Integration Studio or a streaming integration service using the Streaming Integration Tooling. Refer to the [documentation on Creating an API Using a Service]({{base_path}}/api-design-manage/design/create-api/create-an-api-using-a-service).

**Create a GraphQL API**

Expand All @@ -48,11 +48,11 @@ Rate Limiting allows you to limit the number of successful hits to an API during

**Authentication**

API authentication is a way of protecting API access from unidentified or anonymous access. It ensures that the API is secured and accessible only by the consumers who proves their identity and whose identities are found within the API Management Platform. Please refer to [an overview of Authentication]({{base_path}}/api-security/runtime/api-authentication/api-authentication-overview) for more information.
API authentication is a way of protecting API access from unidentified or anonymous access. It ensures that the API is secured and accessible only by the consumers who prove their identity and whose identities are found within the API Management Platform. Please refer to [an overview of Authentication]({{base_path}}/api-security/runtime/api-authentication/api-authentication-overview) for more information.

**Authorization**

Due to the expanding consumer base, the application developers have to focus on limiting the API access in order to make sure that only the authorized parties have access to respective resources/services. Please refer to [an overview of Authorization in API Manager]({{base_path}}/api-security/runtime/authorization/api-authorization) for more information.
Due to the expanding consumer base, the application developers have to focus on limiting the API access in order to make sure that only the authorized parties have access to the respective resources/services. Please refer to [an overview of Authorization in API Manager]({{base_path}}/api-security/runtime/authorization/api-authorization) for more information.

**Threat Protection**

Expand All @@ -62,10 +62,10 @@ There are various threat protectors like Gateway Threat Protectors, Regular Expr

API documentation helps API subscribers to understand the functionality of the API and API publishers to market their APIs better and sustain competition. Using the API Publisher, you can add different types of documentation from various sources. Refer to [documentation on documenting APIs]({{base_path}}/api-design-manage/design/api-documentation/add-api-documentation) for more information.

### Test APIs
## Test APIs

You can test APIs directly in the API Publisher itself. Refer to [documentation on testing REST APIs]({{base_path}}/api-design-manage/design/create-api/create-rest-api/test-a-rest-api) for more information.

### API Revisions
## API Revisions

API Revisions can be used when an API Publisher needs to keep track of different deployments of the API. Refer to [documentation on API Revisions]({{base_path}}/api-design-manage/design/create-api/create-api-revisions) for more information.