You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: articles/api-management/import-and-publish.md
+12-12Lines changed: 12 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,11 +16,11 @@ ms.date: 04/20/2020
16
16
ms.author: apimpm
17
17
18
18
---
19
-
# Import and publish your first API
19
+
# Import and publish your first API
20
20
21
21
This tutorial shows how to import an OpenAPI Specification backend API in JSON format into Azure API Management. Microsoft provides the backend API and hosts it on Azure at [https://conferenceapi.azurewebsites.net?format=json](https://conferenceapi.azurewebsites.net?format=json).
22
22
23
-
Once you import the backend API into API Management, your API Management API becomes a facade for the backend API. You can customize the facade to your needs in API Management without touching the backend API. For more information, see [Transform and protect your API](transform-api.md).
23
+
Once you import the backend API into API Management, your API Management API becomes a facade for the backend API. You can customize the facade to your needs in API Management without touching the backend API. For more information, see [Transform and protect your API](transform-api.md).
24
24
25
25
In this tutorial, you learn how to:
26
26
@@ -40,15 +40,15 @@ In this tutorial, you learn how to:
40
40
## <aname="create-api"> </a>Import and publish a backend API
41
41
42
42
This section shows how to import and publish an OpenAPI Specification backend API.
43
-
43
+
44
44
1. In the left navigation of your API Management instance, select **APIs** from the **API Management** section.
45
45
1. Select the **OpenAPI** tile, and then select **Full** on the pop-up screen.
46
46
1. On the **Create from OpenAPI specification** screen, use the values from the following table to create your API.
47
-
48
-
A red star next to a field on the form indicates that the field is required. You can set API values during creation or later by going to the **Settings** tab.
49
-
47
+
48
+
A red star next to a field on the form indicates that the field is required. You can set API values during creation or later by going to the **Settings** tab.
49
+
50
50

51
-
51
+
52
52
|Setting|Value|Description|
53
53
|-------|-----|-----------|
54
54
|**OpenAPI specification**|*https:\//conferenceapi.azurewebsites.net?format=json*|The service implementing the API. API management forwards requests to this address.|
@@ -59,12 +59,12 @@ This section shows how to import and publish an OpenAPI Specification backend AP
59
59
|**API URL suffix**|*conference*|The suffix appended to the base URL for the API Management service. API Management distinguishes APIs by their suffix, so the suffix must be unique for every API for a given publisher.|
60
60
|**Tags**||Tags for organizing APIs for searching, grouping, or filtering.|
61
61
|**Products**|**Unlimited**|Association of one or more APIs. Each API Management instance comes with two sample products: **Starter** and **Unlimited**. You publish an API by associating the API with a product, **Unlimited** in this example.<br/>You can include several APIs in a product and offer them to developers through the developer portal. To add this API to another product, type or select the product name. Repeat this step to add the API to multiple products. You can also add APIs to products later from the **Settings** page.<br/>To get access to the API, developers must first subscribe to a product. When they subscribe, they get a subscription key that's good for any API in that product. <br/>If you created the API Management instance, you're an administrator already, so you're subscribed to every product in the instance.|
62
-
|**Gateways**|**Managed**|API gateway(s) that expose the API. This field is available only in **Developer** and **Premium** tier services.<br/>**Managed** gateway indicates the gateway built-into the API Management service and hosted by Microsoft in Azure. Other gateways are [self-hosted gateways](self-hosted-gateway-overview.md) and are available only in the Premium and Developer service tiers. You can deploy them in Microsoft Azure, on premises, or in other clouds.<br/>If no gateways are selected, the API won't be available and your API requests won't succeed.|
62
+
|**Gateways**|**Managed**|API gateway(s) that expose the API. This field is available only in **Developer** and **Premium** tier services.<br/>**Managed** gateway indicates the gateway built-into the API Management service and hosted by Microsoft in Azure. Other gateways are [self-hosted gateways](self-hosted-gateway-overview.md) and are available only in the Premium and Developer service tiers. You can deploy them in on premises or in other clouds.<br/>If no gateways are selected, the API won't be available and your API requests won't succeed.|
63
63
|**Version this API?**|Select or deselect|For more information about versioning, see [Publish multiple versions of your API](api-management-get-started-publish-versions.md).|
64
-
64
+
65
65
> [!NOTE]
66
66
> To publish the API to API consumers, you must associate it with a product.
67
-
67
+
68
68
2. Select **Create**.
69
69
70
70
If you have problems importing an API definition, see the [list of known issues and restrictions](api-management-api-import-restrictions.md).
@@ -76,9 +76,9 @@ You can call API operations directly from the Azure portal, which provides a con
76
76
1. In the left navigation of your API Management instance, select **APIs** from the **API Management** section, and then select **Demo Conference API**.
77
77
1. Select the **Test** tab, and then select **GetSpeakers**. The page shows **Query parameters** and **Headers**, if any. The **Ocp-Apim-Subscription-Key** is filled in automatically for the subscription key associated with this API.
78
78
1. Select **Send**.
79
-
79
+
80
80

81
-
81
+
82
82
The back end responds with **200 OK** and some data.
0 commit comments