Merge pull request #1621 from laujan/add-rest-api

Add rest api

Author: v-dirichards

articles/ai-services/content-understanding/audio/overview.md

@@ -63,9 +63,9 @@ Content Understanding offers advanced audio capabilities, including:
 
 Content Understanding offers customizable audio analyzer templates:
 
-* **Post-call analytics**. Analyze call recordings to generate conversation transcripts, call summaries, sentiment assessments, and more.
+* **Post-call analysis**. Analyze call recordings to generate conversation transcripts, call summaries, sentiment assessments, and more.
 
-* **Conversation summarization**. Generate transcriptions, summaries, and sentiment assessments from conversation audio recordings.
+* **Conversation analysis**. Generate transcriptions, summaries, and sentiment assessments from conversation audio recordings.
 
 Start with a template or create a custom analyzer to meet your specific business needs.
 

articles/ai-services/content-understanding/index.yml

@@ -20,7 +20,7 @@ landingContent:
           - text: What is Azure AI Content Understanding?
             url: overview.md
           - text: Azure AI Content Understanding REST API
-            url: /rest/api/aiservices/
+            url: /rest/api/contentunderstanding/operation-groups?view=rest-contentunderstanding-2024-12-01-preview&preserve-view=true
           - text: FAQ
             url: faq.yml
 
@@ -58,7 +58,7 @@ landingContent:
       - linkListType: whats-new
         links:
         - text: "What's new in Azure AI Content Understanding?"
-          url: whats-new.md         
+          url: whats-new.md
 
   - title: Reference
     linkLists:
@@ -68,6 +68,6 @@ landingContent:
             url: service-limits.md
           - text: Language and region support
             url: language-region-support.md
-            
 
-  
+
+

articles/ai-services/content-understanding/quickstart/use-ai-foundry.md

@@ -35,7 +35,7 @@ To follow is an example of building an analyzer to extract key data from an invo
 
 1. Upload a sample file of an invoice document or any other data relevant to your scenario.
 
-  :::image type="content" source="../media/analyzer-template/define-schema-upload.png" alt-text="Screenshot of upload step in user experience.":::
+   :::image type="content" source="../media/analyzer-template/define-schema-upload.png" alt-text="Screenshot of upload step in user experience.":::
 
 1. Content Understanding suggests analyzer templates based on your content type. For this example, select **Document analysis** and build your own schema tailored to the invoice scenario. When using your own data, select the analyzer template that best fits your needs, or create your own. See Analyzer templates for a full list of available templates.
 
@@ -122,5 +122,5 @@ To follow are several of our video analyzer templates.
 
 ## Next steps
 
-* In this quickstart, you learned how to create an analyzer in Azure AI Foundry. To use [REST API](/rest/api/aiservices/), *see* the [REST API quickstart](use-rest-api.md).
+* In this quickstart, you learned how to create an analyzer in Azure AI Foundry. To use [REST API](/rest/api/contentunderstanding/operation-groups?view=rest-contentunderstanding-2024-12-01-preview&preserve-view=true), *see* the [REST API quickstart](use-rest-api.md).
 

articles/ai-services/content-understanding/quickstart/use-rest-api.md

@@ -12,13 +12,13 @@ ms.date: 11/19/2024
 
 # Quickstart: Azure AI Content Understanding REST APIs
 
-* Start using the latest preview version of the Azure AI Content Understanding [REST API (2024-12-01-preview)](/rest/api/aiservices/).
+* Start using the latest preview version of the Azure AI Content Understanding [REST API (2024-12-01-preview)](/rest/api/contentunderstanding/operation-groups?view=rest-contentunderstanding-2024-12-01-preview&preserve-view=true).
 
 * Azure AI Content Understanding is a new generative AI-based [**Azure AI Service**](../../what-are-ai-services.md) that analyzes files of any modality (documents, images, videos, and audio) and extracts structured output in user-defined field formats.
 
 * Integrate the Content Understanding service into your workflows and applications easily by calling our REST APIs.
 
-* This quickstart guides you through using the [Content Understanding REST API](/rest/api/aiservices/) to create a custom analyzer and extract content and fields from your input.
+* This quickstart guides you through using the [Content Understanding REST API](/rest/api/contentunderstanding/operation-groups?view=rest-contentunderstanding-2024-12-01-preview&preserve-view=true) to create a custom analyzer and extract content and fields from your input.
 
 ## Prerequisites
 
@@ -542,6 +542,6 @@ The 200 (`OK`) JSON response includes a `status` field indicating the status of
 
 ## Next steps 
 
-* In this quickstart, you learned how to call the [REST API](/rest/api/aiservices/) to create a custom analyzer. For a user experience, try [**Azure AI Foundry**](https://ai.azure.com/). 
+* In this quickstart, you learned how to call the [REST API](/rest/api/contentunderstanding/operation-groups?view=rest-contentunderstanding-2024-12-01-preview&preserve-view=true) to create a custom analyzer. For a user experience, try [**Azure AI Foundry**](https://ai.azure.com/). 
 
 

articles/ai-services/content-understanding/service-limits.md

@@ -92,7 +92,7 @@ The following limits apply as of version 2024-12-01-preview.
 Classification fields can be defined to return either a single category (single-label classification) or multiple categories (multi-label classification).
 
 * **Single-label classification**: Defined using a string field with the `classify` method. It can be a top-level basic field or a subfield within a group or table.
-* **Multi-label classification**: Represented as a list of string fields with the `classify` method. In the [REST API](/rest/api/aiservices/), `method=classify` and `enum` are specified on the inner string field and can only be a top-level field.
+* **Multi-label classification**: Represented as a list of string fields with the `classify` method. In the [REST API](/rest/api/contentunderstanding/operation-groups?view=rest-contentunderstanding-2024-12-01-preview&preserve-view=true), `method=classify` and `enum` are specified on the inner string field and can only be a top-level field.
 
 *Note: Document analyzers currently don't support classification fields.*
 

articles/ai-services/content-understanding/toc.yml

@@ -46,9 +46,15 @@ items:
   - name: Video
     href: video/overview.md
     displayName: video, audio, voice, recognition, synthesis, speaker, identification, verification, diarization, transcription, translation, language, understanding, sentiment, analysis, emotion, detection, pronunciation, model
-- Name: Reference
+- name: Responsible AI
+  items:
+    - name: Transparency note
+      href: /legal/cognitive-services/content-understanding/transparency-note?toc=/azure/ai-services/content-understanding/toc.json&bc=/azure/ai-services/content-understanding/breadcrumb/toc.json
+    - name: Data, privacy, and security
+      href: /legal/cognitive-services/content-understanding/data-privacy?toc=/azure/ai-services/content-understanding/toc.json&bc=/azure/ai-services/content-understanding/breadcrumb/toc.json
+- name: Reference
   items:
   - name: REST API
     displayName: quota, tiers, throttle, max, adjustments, requests, support, ocr
-    href: /rest/api/aiservices/
+    href: /rest/api/contentunderstanding/operation-groups?view=rest-contentunderstanding-2024-12-01-preview&preserve-view=true