Designs

Replace a design (keeps history)

Scope: write. The previous state is snapshotted into the revision history with the key's label as the author ("via key nightly-optimizer"), exactly as a save in the editor snapshots the state it replaces.

put/v1/designs/{id}

Request

  • Base URL: https://electronics-architect.com
  • URL: https://electronics-architect.com/v1/designs/{id}
  • Auth: HTTP bearer

Request body

namestring
designDesign required(unresolved $ref)
messagestring

A note describing the design you are SENDING. It is stored with this state and travels with it into the revision history when a later save replaces it; it does not label the state you are replacing.

Response

Updated.

idstring
namestring
versioninteger

The live design's version after this update: a new design is 1 and every update adds 1. The state it replaced is kept as revision version − 1.

updatedAtstring date-time
revisionAuthorstring
editorUrlstring

The deep link that opens this design on the canvas (/app?design=<id>), where the change is flagged as this key's and the previous state is one click away.

Changes

No recorded changes to this operation across all 1 revision of this API.