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/azure-video-indexer/video-indexer-use-apis.md
+12-17Lines changed: 12 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -22,30 +22,24 @@ Before you start, see the [Recommendations](#recommendations) section (that foll
22
22
23
23
1. Sign in to [Azure Video Indexer Developer Portal](https://api-portal.videoindexer.ai/).
24
24
25
-
Review a release note regarding [login information](release-notes.md#october-2020).
26
-
27
-

28
-
29
25
> [!Important]
30
26
> * You must use the same provider you used when you signed up for Azure Video Indexer.
31
27
> * Personal Google and Microsoft (Outlook/Live) accounts can only be used for trial accounts. Accounts connected to Azure require Azure AD.
32
28
> * There can be only one active account per email. If a user tries to sign in with [email protected] for LinkedIn and later with [email protected] for Google, the latter will display an error page, saying the user already exists.
33
-
34
-
2. Subscribe.
35
-
36
-
Select the [Products](https://api-portal.videoindexer.ai/products) tab. Then, select Authorization and subscribe.
37
29
38
-

30
+

31
+
1. Subscribe.
32
+
33
+
Select the [Products](https://api-portal.videoindexer.ai/products) tab. Then, select **Authorization** and subscribe.
39
34
40
35
> [!NOTE]
41
36
> New users are automatically subscribed to Authorization.
42
37
43
-
After you subscribe, you can find your subscription under **Products** -> **Profile**. In the subscription page, you will find the primary and secondary keys. The keys should be protected. The keys should only be used by your server code. They shouldn't be available on the client side (.js, .html, and so on).
38
+
After you subscribe, you can find your subscription under **[Products](https://api-portal.videoindexer.ai/products)** -> **Profile**. In the subscriptions section, you'll find the primary and secondary keys. The keys should be protected. The keys should only be used by your server code. They shouldn't be available on the client side (.js, .html, and so on).
44
39
45
40

46
41
47
-
> [!TIP]
48
-
> Azure Video Indexer user can use a single subscription key to connect to multiple Azure Video Indexer accounts. You can then link these Azure Video Indexer accounts to different Media Services accounts.
42
+
An Azure Video Indexer user can use a single subscription key to connect to multiple Azure Video Indexer accounts. You can then link these Azure Video Indexer accounts to different Media Services accounts.
49
43
50
44
## Obtain access token using the Authorization API
51
45
@@ -96,6 +90,7 @@ The Account ID parameter is required in all operational API calls. Account ID is
This section lists some recommendations when using Azure Video Indexer API.
@@ -113,18 +108,18 @@ When you're uploading videos by using the API, you have the following options:
113
108
114
109
### Getting JSON output
115
110
116
-
- When you call the API that gets video insights for the specified video, you get a detailed JSON output as the response content. [See details about the returned JSON in this topic](video-indexer-output-json-v2.md).
111
+
- When you call the API that gets video insights for the specified video, you get a detailed JSON output as the response content. [See details about the returned JSON in this article](video-indexer-output-json-v2.md).
117
112
- The JSON output produced by the API contains `Insights` and `SummarizedInsights` elements. We highly recommend using `Insights` and not using `SummarizedInsights` (which is present for backward compatibility).
118
-
- We do not recommend that you use data directly from the artifacts folder for production purposes. Artifacts are intermediate outputs of the indexing process. They are essentially raw outputs of the various AI engines that analyze the videos; the artifacts schema may change over time.
113
+
- We don't recommend that you use data directly from the artifacts folder for production purposes. Artifacts are intermediate outputs of the indexing process. They're essentially raw outputs of the various AI engines that analyze the videos; the artifacts schema may change over time.
119
114
120
-
It is recommended that you use the [Get Video Index](https://api-portal.videoindexer.ai/api-details#api=Operations&operation=Get-Video-Index) API, as described in [Get insights and artifacts produced by the API](video-indexer-output-json-v2.md#get-insights-produced-by-the-api) and **not** [Get-Video-Artifact-Download-Url](https://api-portal.videoindexer.ai/api-details#api=Operations&operation=Get-Video-Artifact-Download-Url).
115
+
It's recommended that you use the [Get Video Index](https://api-portal.videoindexer.ai/api-details#api=Operations&operation=Get-Video-Index) API, as described in [Get insights and artifacts produced by the API](video-indexer-output-json-v2.md#get-insights-produced-by-the-api) and **not** [Get-Video-Artifact-Download-Url](https://api-portal.videoindexer.ai/api-details#api=Operations&operation=Get-Video-Artifact-Download-Url).
121
116
122
117
## Code sample
123
118
124
119
The following C# code snippet demonstrates the usage of all the Azure Video Indexer APIs together.
125
120
126
121
> [!NOTE]
127
-
> The following sample is intended for Classic accounts only and not compatible with ARM accounts. For an updated sample for ARM please see [this ARM sample repo](https://github.com/Azure-Samples/media-services-video-indexer/blob/master/ApiUsage/ArmBased/Program.cs).
122
+
> The following sample is intended for classic accounts only and not compatible with ARM-based accounts. For an updated sample for ARM (recommended), see [this ARM sample repo](https://github.com/Azure-Samples/media-services-video-indexer/blob/master/ApiUsage/ArmBased/Program.cs).
0 commit comments