Skip to content

Latest commit

 

History

History
106 lines (74 loc) · 3.71 KB

File metadata and controls

106 lines (74 loc) · 3.71 KB
title azureDataLakeConnector: getUploadSession
description Retrieve an upload session used to supply file-based data to an inbound flow.
author mlafleur
ms.localizationpriority medium
ms.subservice industry-data-etl
doc_type apiPageType
ms.date 04/05/2024

azureDataLakeConnector: getUploadSession

Namespace: microsoft.graph.industryData

[!INCLUDE beta-disclaimer]

Retrieve an upload session used to supply file-based data to an inbound flow.

Permissions

Choose the permission or permissions marked as least privileged for this API. Use a higher privileged permission or permissions only if your app requires it. For details about delegated and application permissions, see Permission types. To learn more about these permissions, see the permissions reference.

[!INCLUDE permissions-table]

HTTP request

GET /external/industryData/dataConnectors/{industryDataConnectorId}/microsoft.graph.industryData.azureDataLakeConnector/getUploadSession

Function parameters

In the request URL, provide the following query parameters with values.

Parameter Type Description
resetSession Boolean True indicates that a new microsoft.graph.industryData.fileUploadSession with an empty container is returned.

Request headers

Name Description
Authorization Bearer {token}. Required. Learn more about authentication and authorization.

Request body

Don't supply a request body for this method.

Response

If successful, this function returns a 200 OK response code and a microsoft.graph.industryData.fileUploadSession in the response body.

Examples

Request

The following example shows a request.

GET https://graph.microsoft.com/beta/external/industryData/dataConnectors/51dca0a0-85f6-4478-f526-08daddab2271/microsoft.graph.industryData.azureDataLakeConnector/getUploadSession

[!INCLUDE sample-code] [!INCLUDE sdk-documentation]


Response

The following example shows the response.

Note: The response object shown here might be shortened for readability.

HTTP/1.1 200 OK
Content-Type: application/json

{
  "containerExpirationDateTime": "2022-12-16T06:07:39.3096785Z",
  "containerId": "40fe691e-a4b8-4b47-8c86-08daddab241e",
  "sessionExpirationDateTime": "2022-12-14T20:07:39.5792917Z",
  "sessionUrl": "https://azureBlobSas.example/"
}