Skip to main content
PATCH
Change a shape
Pomerado rewrites and checks the code as it does for a new shape; a change it can’t make answers as making one does and keeps the shape as it was. Runs already accepted keep the version they started with.

Authorizations

Authorization
string
header
required

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

Path Parameters

id
string
required

a shape ID: shp_ and 32 lowercase hex digits

Example:

"shp_0f8e2d1c4b3a49e8a7f6e5d4c3b2a190"

Body

application/json
request
string

The result you want, in your own words: which fields, renamed how, filtered, sorted, counted or averaged, such as "only the name and price in dollars, cheapest first"

Required string length: 1 - 2000
name
string

A new name for the shape

Required string length: 1 - 120

Response

The changed shape, or why it wasn't changed

outcome
enum<string>
required
Available options:
saved
shape
object
required
preview
any
required

The shape's result for a made-up result of the tool

message
string
required

What happened, in words