REST API

Basics

Welcome

Welcome to the Flex.io API!

With the Flex.io API, you can build, save, and invoke sequences of tasks, called pipes, that take an input, process it, and return an output.

Pipes are pretty flexible. You can define and use pipes inline in your code, or you can define and save them in one place and then invoke them repeatedly with different sets of parameters elsewhere.

Pipes can be shared with others, allowing them to invoke these pipes with parameters they supply while giving you the ability to quickly create cloud functions for use by you and others. You can also define pipes that use connections that let you read and write to various cloud services while keeping credentials hidden.

You can find the API documentation below. However, also check out the Getting Started Guide for an introduction to building and deploying pipes.

OK, let’s get started!

Base URL

The base URL for all API requests is: https://api.flex.io/v1

For example, to get information about Flex.io:

Versioning

The API version is included in the base URL of the request. The current version is v1.

Authentication

API requests are made over HTTPS and authenticated with an API key. This API key is supplied as the {token} in an HTTP Authorization header: Authorization: Bearer {token}

To get your API key:

  1. Sign up or sign in if you already have an account.
  2. Copy the API key from your Dashboard.
  3. You can also get and manage your API key from your Account.

Once you have your API key, you can try a basic request to return your user information:

  1. Create an HTTP GET request to https://api.flex.io/v1/me/account.
  2. Set the HTTP Authorization header Authorization: Bearer {token} using your API key in place of {token}

Here’s what it looks like:

Requests

Basic Concepts

The Flex.io API is organized around REST: pipes, connections, and other resources are accessed with URL endpoints and manipulated using HTTP GET, POST, and DELETE verbs. GET is used for reading resources, POST is used for creating and updating resources, and DELETE is used for deleting resources.

In general, resources identifiers are specified in the URL. In cases where objects are being created or updated, additional parameters are sent in the request body.

When reading, updating, or deleting existing resources, resource identifiers are specified in the URL. Following are some examples showing basic CRUD operations on a pipe.

To create a pipe:

To read a pipe:

To update a pipe:

To delete a pipe:

Headers

When making all requests, the authorization header must be set and include the API key in the token portion of the authorization header: Authorization: Bearer {token}

In addition, when making requests that create or update a resource, parameters are sent as JSON in the POST request and the content type header must be set to the JSON content type: Content-Type: application/json

Cross Origin Sharing

The Flex.io supports Cross Origin Resource Sharing (CORS), so you can make requests from any location.

Rate Limits

If you exceed your rate limitations, you may get a rate limit error. We expect you won’t encounter rate limits in normal usage.

Responses

Basic Concepts

In most cases, responses are returned as JSON, and the HTTP status code indicates success or failure. In general, response codes in the 200-level range indicate success, response codes in the 400-level range indicate a failure caused by a request that can’t be fulfilled even though the Flex.io service is working as expected, and response codes in the 500-level range indicate a failure caused by a problem with the Flex.io service itself.

HTTP status codes have the following meanings:

Code Meaning
200 OK
400 Bad request
401 Unauthorized
403 Forbidden
404 Not found
422 Unprocessable entity
500 Internal server error

Errors

When a response indicates a failure with an HTTP status code, the body of the response will contain an error object with additional information about the error. The error object contains at least two parameters: a code that indicates the type of error and a message that provides a description of the error.

For example, if you make the following request to an invalid API endpoint, you’ll get an error object that indicates an invalid request:

Following are a list of the error codes:

Code Description
general General problem that doesn’t have more specific information
unimplemented A request is made contains a feature that isn’t implemented
deprecated A request is made for a feature that is deprecated
invalid-version A request is made that isn’t for a valid API version
invalid-request A request is made on an API endpoint that isn’t available
invalid-syntax A request is made with syntax that isn’t valid
missing-parameter A request doesn’t contain a parameter that’s needed
invalid-parameter A request contains a parameter that’s in the wrong format
unauthorized A request is made for a resource that isn’t public, and the request doesn’t have any authorization information to check the access rights
insufficient-rights A request is made for a resource that isn’t public, and the request isn’t authorizated to access the resource
rate-limit-exceeded A request is made that exceeds the rate limit
size-limit-exceeded A request is made that exceeds the size limit
integrity-failed An operation involves an integrity check, and the entity being checked fails to match a supplied integrity check value
connection-failed An operation involves making a connection, but the process of connecting fails
create-failed An operation involves creating something, but the process of creating it fails
read-failed An operation involves reading something, but the process of reading it fails
write-failed An operation involves writing to something, but the process of writing to it fails
delete-failed An operation involves deleting something, but the process of deleting it fails
no-database Server error indicating a database isn’t available
no-model Server error indicating a model isn’t available
no-service Server error indicating a service isn’t available
no-object Server error indicating an object isn’t available

Pagination

Requests returning lists of items will return all the items in the list.

Pipes

Overview

Pipes are made up a series of tasks that run sequentially. Pipe input is passed to the first task, then the output of that task is passed to the next task and so on, until the tasks are finished and the pipe returns the resulting output.

Pipes support a variety of different tasks. For example, pipes may include tasks that can execute Python or Javascript code, make requests from APIs directly or from connections that hide API credentials, as well as perform operations on data, such as converting from one format to another. We’ll see how to add tasks to pipes later as well as a complete list of what tasks are possible.

Once you’ve defined a pipe, you can save it with an identifier, and then invoke it as a cloud function with this identifier, passing it parameters you supply when invoking it. For example, you might create a pipe that you call ‘verified-content’ that takes POST parameters, takes these parameters and verifies them with a remotely defined and sha-checked python function, then POSTs the verified parameters to an API endpoint. Once you’ve defined this pipe and saved it, you can run this pipe using the ‘verified-content’ identifier and use it to pass parameters that are verified to the API endpoint.

GET /pipes

Description

Gets a list of pipe objects

Response

Property Type Description
eid string auto-generated object identifier
eid_type string object type
eid_status string object status
alias string user-defined object identifier
name string pipe name
description string pipe description
owned_by object owner of the pipe
task object task object making up the pipe logic
schedule object schedule information for when the pipe will run
schedule_status string schedule status indicating whether or not a pipe is scheduled; if the schedule status is ‘A’, the pipe is scheduled, and if the schedule status is ‘I’, then the pipe is unscheduled; if the schedule status is unspecified, it defaults to the unscheduled status
created string date when the object was created in ISO 8601 format
updated string date when the object was last updated in ISO 8601 format

Example

POST /pipes

Description

Creates a pipe and returns the newly created pipe object with the pipe properties

Body Parameters

Property Type Description
eid_status string object status; if the status is ‘P’, it is pending and will not appear in the active list of pipes, but can still have it’s properties set; if the status is ‘A’, it is active and will appear in the list of pipes; if the status is ‘T’ it is trashed and will appear in the list of trashed items; if the status is ‘D’, it is deleted and will not appear in any list
alias string user-defined object identifier; if the alias is specified, it must be a globally unique, and a valid string; to avoid name clashes, we recommend you use your username as a prefix for aliases you choose
name string pipe name
description string pipe description
task object task object making up the pipe logic
schedule object schedule information for when the pipe will run
schedule_status string schedule status indicating whether or not a pipe is scheduled; if the schedule status is ‘A’, the pipe is scheduled, and if the schedule status is ‘I’, then the pipe is unscheduled; if the schedule status is unspecified, it defaults to the unscheduled status

Response

Property Type Description
eid string auto-generated object identifier
eid_type string object type
eid_status string object status
alias string user-defined object identifier
name string pipe name
description string pipe description
owned_by object owner of the pipe
task object task object making up the pipe logic
schedule object schedule information for when the pipe will run
schedule_status string schedule status indicating whether or not a pipe is scheduled; if the schedule status is ‘A’, the pipe is scheduled, and if the schedule status is ‘I’, then the pipe is unscheduled; if the schedule status is unspecified, it defaults to the unscheduled status
created string date when the object was created in ISO 8601 format
updated string date when the object was last updated in ISO 8601 format

Example

GET /pipes/{id}

Description

Gets a single pipe object

Path Parameters

Property Type Description
id string unique object identifier; either the auto-generated eid object identifier, or the user-defined alias object identifier

Response

Property Type Description
eid string auto-generated object identifier
eid_type string object type
eid_status string object status
alias string user-defined object identifier
name string pipe name
description string pipe description
owned_by object owner of the pipe
task object task object making up the pipe logic
schedule object schedule information for when the pipe will run
schedule_status string schedule status indicating whether or not a pipe is scheduled; if the schedule status is ‘A’, the pipe is scheduled, and if the schedule status is ‘I’, then the pipe is unscheduled; if the schedule status is unspecified, it defaults to the unscheduled status
created string date when the object was created in ISO 8601 format
updated string date when the object was last updated in ISO 8601 format

Example

POST /pipes/{id}

Description

Updates a pipe with the specified values and returns the pipe object with the updated pipe properties

Path Parameters

Property Type Description
id string unique object identifier; either the auto-generated eid object identifier, or the user-defined alias object identifier

Body Parameters

Property Type Description
eid_status string object status; if the status is ‘P’, it is pending and will not appear in the active list of pipes, but can still have it’s properties set; if the status is ‘A’, it is active and will appear in the list of pipes; if the status is ‘T’ it is trashed and will appear in the list of trashed items; if the status is ‘D’, it is deleted and will not appear in any list
alias string user-defined object identifier; if the alias is specified, it must be a globally unique, and a valid string; to avoid name clashes, we recommend you use your username as a prefix for aliases you choose
name string pipe name
description string pipe description
task object task object making up the pipe logic
schedule object schedule information for when the pipe will run
schedule_status string schedule status indicating whether or not a pipe is scheduled; if the schedule status is ‘A’, the pipe is scheduled, and if the schedule status is ‘I’, then the pipe is unscheduled; if the schedule status is unspecified, it defaults to the unscheduled status

Response

Property Type Description
eid string auto-generated object identifier
eid_type string object type
eid_status string object status
alias string user-defined object identifier
name string pipe name
description string pipe description
owned_by object owner of the pipe
task object task object making up the pipe logic
schedule object schedule information for when the pipe will run
schedule_status string schedule status indicating whether or not a pipe is scheduled; if the schedule status is ‘A’, the pipe is scheduled, and if the schedule status is ‘I’, then the pipe is unscheduled; if the schedule status is unspecified, it defaults to the unscheduled status
created string date when the object was created in ISO 8601 format
updated string date when the object was last updated in ISO 8601 format

Example

DELETE /pipes/{id}

Description

Deletes the pipe and returns basic identifier and status information for the pipe that was deleted

Path Parameters

Property Type Description
id string unique object identifier; either the auto-generated eid object identifier, or the user-defined alias object identifier

Response

Property Type Description
eid string auto-generated object identifier
eid_type string object type
eid_status string object status

Example

POST /pipes/{id}/run

Description

Runs a pipe, processing any data that’s posted with the logic specified in the pipe, and returning the results of the process

Path Parameters

Property Type Description
id string unique object identifier; either the auto-generated eid object identifier, or the user-defined alias object identifier

Body Parameters

Property Type Description
data string in addition to the basic identifier information, any other form data can be posted to the pipe for processing; this data can be used for both controlling how the pipe runs as well as the data itself that the pipe processes

Response

The response is the user-defined output of the pipe. For example, if the pipe echos ‘Hello, world!’ to stdout in the pipe logic, then the result will be ‘Hello, world!’.

Example

Connections

Overview

Connections are collections of information about a resource, such as an API, that can be used by pipes when making requests. This information may include base API URL endpoints, header information such as user agent or content type, or API tokens that are needed to access the API.

Connections allow pipes to define and make HTTP requests using the connection info without exposing API tokens, and without having to define the connection info each time a request is defined in the pipe.

GET /connections

Description

Gets a list of connection objects

Response

Property Type Description
eid string auto-generated object identifier
eid_type string object type
eid_status string object status
alias string user-defined object identifier
name string connection name
description string connection description
connection_type string type of connection
connection_status string status of the connection
connection_info object connection info associated with the connection
expires string expiration date of the connection
owned_by object owner of the connection
created string date when the object was created in ISO 8601 format
updated string date when the object was last updated in ISO 8601 format

Example

POST /connections

Description

Creates a new connection and returns the newly created connection object

Body Parameters

Property Type Description
eid_status string object status; if the status is ‘P’, it is pending and will not appear in the active list of connections, but can still have it’s properties set; if the status is ‘A’, it is active and will appear in the list of connections; if the status is ‘T’ it is trashed and will appear in the list of trashed items; if the status is ‘D’, it is deleted and will not appear in any list
alias string user-defined object identifier; if the alias is specified, it must be a globally unique, and a valid string; to avoid name clashes, we recommend you use your username as a prefix for aliases you choose
name string connection name
description string connection description
connection_type string connection type indicator; ‘http’ for HTTP connections
connection_status string connection status; if the connection is available, the connection status is ‘A’; if the connection is unavailable, the connection status is ‘U’; if the connection status has an error of some kind, the connection status is ‘E’
connection_info object information assoeicated with the connection; for example, for http connections, this will include the base url of the connection as well as http header information; when this connection is used in a pipe request, this connection info will be applied to the request being made in the pipe

Response

Property Type Description
eid string auto-generated object identifier
eid_type string object type
eid_status string object status
alias string user-defined object identifier
name string connection name
description string connection description
connection_type string type of connection
connection_status string status of the connection
connection_info object connection info associated with the connection
expires string expiration date of the connection
owned_by object owner of the connection
created string date when the object was created in ISO 8601 format
updated string date when the object was last updated in ISO 8601 format

Example

GET /connections/{id}

Description

Gets a single connection object

Path Parameters

Property Type Description
id string unique object identifier; either the auto-generated eid object identifier, or the user-defined alias object identifier

Response

Property Type Description
eid string auto-generated object identifier
eid_type string object type
eid_status string object status
alias string user-defined object identifier
name string connection name
description string connection description
connection_type string type of connection
connection_status string status of the connection
connection_info object connection info associated with the connection
expires string expiration date of the connection
owned_by object owner of the connection
created string date when the object was created in ISO 8601 format
updated string date when the object was last updated in ISO 8601 format

Example

POST /connections/{id}

Description

Updates a connection with the specified values and returns the connection object with the updated connection properties

Path Parameters

Property Type Description
id string unique object identifier; either the auto-generated eid object identifier, or the user-defined alias object identifier

Body Parameters

Property Type Description
alias string user-defined object identifier; alternatively, a user-defined alias can be specified in the {id} portion of the request path instead of an eid
name string connection name
description string connection description
connection_type string connection type indicator; ‘http’ for HTTP connections
connection_status string connection status; if the connection is available, the connection status is ‘A’; if the connection is unavailable, the connection status is ‘U’; if the connection status has an error of some kind, the connection status is ‘E’
connection_info object information assoeicated with the connection; for example, for http connections, this will include the base url of the connection as well as http header information; when this connection is used in a pipe request, this connection info will be applied to the request being made in the pipe

Response

Property Type Description
eid string auto-generated object identifier
eid_type string object type
eid_status string object status
alias string user-defined object identifier
name string connection name
description string connection description
connection_type string type of connection
connection_status string status of the connection
connection_info object connection info associated with the connection
expires string expiration date of the connection
owned_by object owner of the connection
created string date when the object was created in ISO 8601 format
updated string date when the object was last updated in ISO 8601 format

Example

DELETE /connections/{id}

Description

Deletes the connection and returns basic identifier and status information for the connection that was deleted

Path Parameters

Property Type Description
id string unique object identifier; either the auto-generated eid object identifier, or the user-defined alias object identifier

Response

Property Type Description
eid string auto-generated object identifier
eid_type string object type
eid_status string object status

Example

Users

Overview

Users are the owners of pipes and connections they create. Users can share their pipes, allowing other users, called followers, to either read, write, or run these pipes, depending on the permissions they are granted. In the same way, users can share their pipes with the public.

GET {user-id}/account

Description

Gets information about the user

Path Parameters

Property Type Description
userid string unique object identifier; either the auto-generated eid object identifier, or the username for the user; the special identifer me can be used as a substitute for your username to return information about yourself

Response

Property Type Description
eid string auto-generated object identifier
eid_type string object type
eid_status string object status
alias string user-defined object identifier
username string user name
first_name string first name
last_name string last name
email string user email
email_hash string MD5 hash of the email
phone string user phone number
location_city string city where user is located
location_state string state where user is located
location_country string country where user is located
company_name string name of the company where the user works
company_url string url of the company where the user works
locale_language string language preference for the user
locale_decimal string decimal preference for the user
locale_thousands string thousands separator preference for the user
locale_dateformat string data format preference for the user
timezone string timezone for the user
config string configuration settings
created string date when the object was created in ISO 8601 format
updated string date when the object was last updated in ISO 8601 format

Example

Tasks

Archive

Description

Creates a zipped or compressed file from stdin or from files.

Parameters

Property Type Description
format string The format of the archive to create; either zip or gzip.

Returns

Returns a zipped or compressed file.

Example

{
"op": "archive",
"format": "gzip"
}

Connect

Description

Creates a connection handle that can be used in other tasks to create, read, write, delete, and list files in cloud storage.

Parameters

Property Type Description
alias string Alias to use when referencing this connection in other tasks.
connection_type string Type of connection to create
connection_info object Key/values necessary to connect to various cloud storage; connection-specific.

Returns

No output.

Example

{
"op": "connect",
"alias": "my-cloud-storage",
"connection_type": "amazons3",
"connection_info": {
"aws_key": "my-aws-key",
"aws_secret": "my-aws-secret",
"bucket": "my-s3-bucket",
"region": "us-east-1"
}
}

Convert

Description

Converts the input from one format to another.

Parameters

Property Type Description
input object Format specifier for the input; the primary parameter for this object is format and may be one of the following: delimited, fixed, json, rss, pdf, table.
output object Format specifier for the output; the primary parameter for this object is format and may be one of the following: delimited, fixed, json, rss, pdf, table.

Returns

Returns the body response for the HTTP request.

Example

{
"op": "convert",
"input": {
"format": "delimited",
"delimiter": "{comma}",
"header": true,
"qualifier": "{none}"
},
"output": {
"format": "json"
}
}

Copy

Description

Copies files and directories from one location to another.

Parameters

Property Type Description
from string The source filespec. This may be a file, directory, or a filespec containing a path wildcard.
to string The target filespec. This may be a file or directory.

Returns

No output.

Example

{
"op": "copy",
"from": "/my-sftp/*.csv",
"to": "/my-cloud-storage/"
}

Create

Description

Creates the specified file.

Parameters

Property Type Description
path string The path of the file to create.
content-type string The content type of the file to be created.

Returns

The created file.

Example

{
"op": "create",
"path": "/my-cloud-storage/file.txt",
"content_type": "text/plain"
}

Delete

Description

Deletes the specified file.

Parameters

Property Type Description
path string The path of the file to delete.

Returns

Example

{
"op": "delete",
"path": "/my-cloud-storage/file.txt"
}

Echo

Description

Writes the specified message to the output.

Parameters

Property Type Description
msg string Value to write to the output.

Returns

Returns the value specified in msg.

Example

{
"op": "echo",
"msg": "Hello, World!"
}

Email

Description

Sends an email.

Parameters

Property Type Description
to string The email address to send the message to.
subject string The subject of the email.
body string The plain text content of the email.
html string The HTML content of the email.
attachments array A list of files to send as attachments to the email. The files to attach are specified as strings and/or objects, where the file path is a connection alias followed by the file path within that connection. If a files is listed as an object, the path of the file to attach is specified in the file property with an optional name and content type being specified with a name and mime_type property respectively.

Returns

Returns the input.

Example

{
"op": "email",
"to": "flexio@mailinator.com",
"subject": "Daily report",
"body": "Attached, please find the latest figures",
"html": "",
"attachments": [
"/my-connection-alias/file1.txt",
{"file": "/my-connection-alias/file2.txt"},
{"file": "/my-connection-alias/file3.txt", "name": "name.txt"},
{"file": "/my-connection-alias/file4.txt", "name": "name.json", "mime_type", "application/json"}
]
}

Execute

Description

Executes code that’s specified inline or in another location, such as a source control repository.

Parameters

Property Type Description
lang string The language to execute, using the path if supplied or the code specifed as base64 content in code; lang may be either ‘javascript’ if the code to execute is Javascript or ‘python’ if the code to execute is Python.
code string The base64-encoded code to execute; takes precendence over any code at path.
path string The URL of the code to execute (e.g. GitHub file URL); if both path and code are specified, the code locally defined in code overrides the code at path.
integrity string The optional integrity check for the code; if the code given by code or located in the remote path doesn’t match the integrity check, then it fails; integrity checks may use either sha256, sha384, or sha512 values and are specified as ‘sha256:{base64-sha256-value}’, ‘sha384:{base64-sha384-value}’ or ‘sha512:{base64-sha512-value}’.

Code to be executed is specified in the code parameter or in the path. This code needs to include a handler function as the main entry point into the code. When an execute task is executed, the code is loaded and checked against supplied integrity value; then the code is run and the handler function is called with a context object.

In Javascript, the handler function is:

exports.flexio_handler = function(context) {}

In Python, the handler function is:

def flexio_handler(context)

The context object is used to exchange information with the pipe process, including reading the output from the previously run step or parameters supplied when the pipe was invoked, as well as writing output to be read by the next task to be run or updating variables to be used in subsequent tasks.

For example, the output from the previous task is passed in through the context objects input parameter and the output from the execute step is passed onto the next task through the output parameter.

Example 1. Javacript handler function that reads input from the previous task and writes it out for the next task:

Example 2. Python handler function that reads input from the previous task and writes it out for the next task:

Returns

Returns the results written to the context object output in the code.

Example

{
"op": "execute",
"lang": "python",
"code": "ZGVmIGZsZXhpb19oYW5kbGVyKGNvbnRleHQpOg0KICAgIGNvbnRleHQub3V0cHV0LmNvbnRlbnRfdHlwZSA9ICJ0ZXh0L3BsYWluIg0KICAgIGNvbnRleHQub3V0cHV0LndyaXRlKCJIZWxsbywgV29ybGQhIik="
}

Exit

Description

Stops the execution of the process.

Parameters

Property Type Description
code integer The HTTP header code to return with the result.
response string The response to send.

Returns

Returns an HTTP header with the assigned code and the response in the HTTP body.

Example

{
"op": "exit",
"code": 404,
"response": "The specified resource does not exist."
}

Filter

Description

Filters the rows of the input, passing on rows that satisfy the where condition.

Parameters

Property Type Description
where string The filter expression to use to determine whether or not to pass on a row from the input to the output.

Returns

Returns the filtered input.

Example

{
"op": "filter",
"where": "'id' = 1"
}

List

Description

Lists the contents of a directory.

Parameters

Property Type Description
path string The path of the directory contents to list.

Returns

Returns the contents of the specified directory.

Example

{
"op": "list",
"path": "/my-connection-alias/directory-in-connection/"
}

Mkdir

Description

Creates the specified directory.

Parameters

Property Type Description
path string The path of the directory to create.

Returns

Example

{
"op": "mkdir",
"path": "/my-connection-alias/directory-in-connection-to-create/"
}

Read

Description

Reads the specified file and outputs its contents.

Parameters

Property Type Description
path string The path of the file to read from.

Returns

Returns the contents of the specified file.

Example

{
"op": "read",
"path": "/my-connection-alias/file.txt"
}

Render

Description

Renders the input from one format to another.

Parameters

Property Type Description
url string The URL of the webpage to render.
format string The format to return the rendered URL in; current options are pdf, png, and jpeg.
paper string The paper size to use when outputting to a PDF; current options are letter and A4.
width string The width in pixels to use when formatting the URL that’s being rendered.
height string The height in pixels to use when formatting the URL that’s being rendered.
full boolean Whether or not to render the entire URL when outputting as an image.
landscape boolean Whether or not to use landscape mode when outputting to a PDF.
scrollbars boolean Whether or not to include scrollbars when rendering the URL.

Returns

Returns the rendered content for the URL.

Example

{
"op": "render",
"url": "https://www.flex.io",
"format": "png",
"width": "800",
"height": "600",
"scrollbars": false
}

Request

Description

Issues an HTTP request.

Parameters

Property Type Description
method string The HTTP method to use when making the request; options are: GET, POST, PUT, PATCH, and DELETE.
url string The URL to issue the request to.
headers object An object where the keys are the HTTP headers to set and the corresponding values are the values of those headers.
username string Any username to use for basic authentication.
password string Any password to use for basic authentication.
params object Data to include as URL parameters in a GET request; these can also be passed in the query string of the URL.
data object|string Data to include in POST, PUT, PATCH, and DELETE requests.
connection string Optional connection identifier to issue the request to; if a connection identifier is specified, parameters specified in the connection object are used as the default settings for the request with any additional parameters overriding the request parameters and any specified url in the request begin appended to the base url specified in the connection.

Returns

Returns the body response for the HTTP request.

Example

{
"method": "POST",
"url": "https://api.flex.io/v1/me/pipes",
"headers": {
"Authorization": "Bearer {token}"
},
"data": {
"name": "Example Pipe",
"description": "Example Pipe Created From Request Task"
}
}

Select

Description

Selects the specified columns and returns only these columns in the result.

Parameters

Property Type Description
columns array An array of the column names to include in the result.

Returns

Returns the selected columns.

Example

{
"op": "select",
"columns": [
"name"
]
}

Unarchive

Description

Unzips or uncompresses a file.

Parameters

Property Type Description
format string The format of the file to uncompress; either zip or gzip.

Returns

Returns the uncompressed files from a compressed file.

Example

{
"op": "unarchive",
"format": "gzip"
}

Write

Description

Writes the input to the specified file.

Parameters

Property Type Description
path string The path of the file to write to.

Returns

Returns the result of the final task in the sequence.

Example

{
"op": "write",
"path": "/my-connection-alias/file.txt"
}