Databricks HTTP Request

Databricks HTTP Request activity in the Databricks connector.

Description

Performs HTTP requests to the Databricks workspace REST API by using the existing connector and connection configuration. Use it to reach Databricks endpoints that the predefined activities do not cover.

Compatibilité du projet

Windows | Multiplate-forme

Configuration

• Connexion : la connexion établie dans Integration Service. Accédez au menu déroulant pour choisir, ajouter ou gérer des connexions.
• Method - The HTTP verb to use: GET, POST, PUT, PATCH, or DELETE.
• Base URL - The workspace base URL. This is read-only and provided by the connection.
• Endpoint - The request path, appended to the base URL. For example, /api/2.1/jobs/list.
• Headers - Request headers.
• Query Parameters - Request query parameters.
• Body - The request body, for methods that accept one.

Remarque :

This activity only accepts application/json as the content type, and does not support file upload or download. To move files in and out of a Unity Catalog volume, use Upload a File and Download a File instead.

Sortie

• Code de statut de la réponse : variable de sortie générée automatiquement.
• En-têtes de réponse : variable de sortie générée automatiquement.
• Corps de la réponse : variable de sortie générée automatiquement.

Remarque :

You might see variations in the output depending on where you run the activity. In API workflows and Maestro Flow, a single response object containing all the fields is returned. In RPA workflows, not all fields are exposed, but you can still retrieve them from the exposed response object.