HTTP Actions
platform.extensions.http-actions
An HTTP action is one request to an external API through an HTTP connector: the method, the path, headers, query parameters and a request body built from the action’s inputs.
To learn what HTTP actions do, see HTTP Actions in the Tool Studio docs.
- Endpoint:
/platform/extensions/http-actions| Methods: GET, PATCH, POST - Request shape: fields go at the top level of the JSON body, with no
resourcewrapper. The item’sidgoes in the URL for reads and updates, not in the body. - Updates: a JSON merge-patch with
version: {num, change_description}from your last read. Lists of objects merge row by row, so read first and send the whole list when you remove or reorder rows. See Tool Studio. - References: Uses an HTTP connector through
connector_id(the connector’sid). Conversational processes, data types and plugins refer to the action by itsid; compound actions refer to it bysignature.name.
Endpoints
All paths are relative to https://api.moveworks.ai/configurations/v1alpha1. Each endpoint page lists the request and response schema, an example, and the errors it can return.
Rules the API checks
methodis required.pathstarts with/and has no query string. Use{{{argument}}}for path parameters andquery_paramsfor the query string.- Up to 250 headers and 250 query parameters.
body_bendertakes the short form of a Data Mapper expression.