Log in to see full request history

Executes an integration (Blend) in a customer account. This creates a run (job) of the integration.
Note that you can reference the Blend by its guid, or by its name. This makes it possible to "find" Blends in multiple accounts, by using unique pre-defined names for Blends.

Note that integrations can also be executed in other ways: blends can be scheduled, they can be triggered through a webhook, or they can be executed manually from the Blendr.io Admin backend.

Use async=false (default) to execute the Blend synchronously, which means the API call will wait for the Blend to finish, and the Blend response will be the response of the API call. When async=true, the API call will create the job but will not wait for the Blend to finish, so the Blend response will not be available. The "async" parameter can be added in the querystring or in the POST body (see example below).

If the Blend has input parameters, add them in the POST body. Example POST body:

{ "async": true, "inputs": { "inputname1": "value1", "inputname2": "value2" } }
Path Params
string
required

External id or guid of the customer account

string
required

Name or guid of the Blend to be executed inside the given customer account

Query Params
boolean
Defaults to false

Optional, default is false. Set to true to execute the Blend asynchronously. Can be in querystring or in post body.

Body Params
json

Input parameters

Responses

Language
Credentials
Click Try It! to start a request and see the response here! Or choose an example:
application/json