Skip to main content
PUT
Offer a workflow as a place to start, or replace what a key offers

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Path Parameters

partnerId
string<uuid>
required

The partner whose starting point to set

key
string
required

The name your code and the picker use for the starting point

Pattern: ^[a-z0-9][a-z0-9_-]{0,63}$

Body

application/json
workflowId
string<uuid>
required

One of your own published workflows.

title
string | null

What the picker shows. Leave it out to show the workflow's name.

Required string length: 1 - 120
description
string | null
Maximum string length: 500
position
integer
default:0

Where it sits in the list. Smallest first; the same position is ordered by key.

Required range: 0 <= x <= 10000

Response

The starting point as saved

success
boolean
required
Example:

true

data
object
required

A workflow you offer as a place to start, and what became of it. People start from it with their own copy of every widget it chains, a composition of their own on each copy, and a draft workflow wired like its live version.

Example:
meta
object

Extra information about the answer: where a page sits in a list, the cursor of the next page, or warnings about a call that succeeded with a caveat.