Improvado

Improvado Automated Recipes API

Deploy and operate automated recipes through the v3.1 API. An automated recipe turns a template into a SQL view in your workspace destination, built from the extractions the template needs. **Deploying a recipe takes four calls, in this order:** 1. `GET /api/v3.1/automated-recipe-templates/` - pick a template. 2. `POST /api/v3.1/automated-recipes/` - create the recipe. It is created empty. 3. `PUT /api/v3.1/automated-recipes/{recipe_id}/` - supply data sources, connections and accounts. **This step is mandatory.** 4. `POST /api/v3.1/automated-recipes/{recipe_id}/build/` - start the build, then poll `GET /api/v3.1/automated-recipes/{recipe_id}/` until `state` is `ready_to_work` or `failed`. Every path ends with a slash; a `301` means the slash is missing from your URL. With a bearer token the workspace is the one the token was issued for; with cookie authentication, send the workspace id in the `X-IM-WORKSPACE-ID` header. All errors use one envelope - see [Errors](/errors). See the [Deploying recipes](/recipes) guide for the full flow.

Documentation GitHub OpenAPI

Operations 10

GET /api/v3.1/automated-recipe-templates/ List recipe templates #

GET /api/v3.1/automated-recipe-templates/{template_id}/ Get a recipe template #

GET /api/v3.1/automated-recipes/ List recipes #

POST /api/v3.1/automated-recipes/ Create a recipe #

GET /api/v3.1/automated-recipes/{recipe_id}/ Get a recipe #

PUT /api/v3.1/automated-recipes/{recipe_id}/ Configure a recipe #

DELETE /api/v3.1/automated-recipes/{recipe_id}/ Delete a recipe #

POST /api/v3.1/automated-recipes/{recipe_id}/build/ Start a recipe build #

POST /api/v3.1/automated-recipes/{recipe_id}/resetup/ Recreate a recipe from its template #

GET /api/v3.1/automated-recipes/{recipe_id}/extractions/ Check recipe extraction tables #

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this

find_apisBrowse and filter every API in the catalog.
get_api_artifactsOne API's artifacts, grouped by type.
get_openapiThe primary OpenAPI for this API.
find_similar_apisAPIs that look like this one.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This API

curl "https://apis.io/api/v1/apis/improvado:improvado-automated-recipes-api"

All apis

curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

OpenAPI Specification

openapi: 3.2.0
info:
  title: Improvado Embedded API v3 Automated Recipes API
  version: 3.0.0
  description: 'Improvado Embedded API V3 provides programmatic access to data extraction, transformation, and loading capabilities.


    ## Authentication


    This API supports multiple authentication methods depending on the endpoint:


    ### Basic Authentication

    Used for workspace-agnostic operations such as:

    - Creating access tokens (`POST /api/v3/token`)

    - Listing workspaces (`GET /api/v3/workspaces`)

    - Managing workspaces (`POST /api/v3/workspaces`, `GET /api/v3/workspaces/{id}`, `PUT /api/v3/workspaces/{id}`)

    - Getting iframe URLs (`POST /api/v3/get_iframe_url`)

    - Listing available recipes (`GET /api/v3/recipes/`)

    etc.


    **Format**: `Authorization: Basic `


    ### Bearer Token Authentication

    Used for workspace-scoped operations after obtaining a token from `/api/v3/token`. The token is scoped to a specific workspace.


    **Format**: `Authorization: Bearer `


    ### Cookie Authentication

    Alternative to Bearer token for browser-based integrations. When using cookie authentication, you must include the workspace ID in the request header.


    **Cookie**: `dts_session_id=`


    **Required Header**: `X-IM-WORKSPACE-ID: `


    ## Workspace Scoping


    Most API operations are workspace-scoped. After authenticating with Basic Auth, obtain a workspace-specific token using `POST /api/v3/token` with the desired `workspace_id`. This token provides access only to resources within that workspace, ensuring isolation between different customers or projects.


    ## Errors


    The automated recipe operations under `/api/v3.1/automated-recipe*` and

    `GET /api/v3.1/connections/{connection_id}/accounts/` return errors as

    `{"code": "...", "message": "...", "details": {...}}`. Branch on `code`, never on the

    message text. See Errors for the catalogue of codes and the shape of `details`.


    All other operations return errors as `{"detail": "error description"}`.'
servers:
- url: https://embedded.improvado.io
tags:


# --- truncated at 32 KB (123 KB total) ---
# Full source: https://raw.githubusercontent.com/api-evangelist/improvado/refs/heads/main/openapi/improvado-automated-recipes-api-openapi.yml