renza

API reference / Decks

Create or upsert a deck

POST/v1/decks

Creates a deck. If `external_id` is provided and already exists in the org, the existing deck is updated instead (200); otherwise a new deck is created (201).

Requires an API key (bearer), scoped to the active org. Supports idempotency keys.

Body parameters

  • titlestringoptionalmax 300 chars
  • statusstringoptional
  • share_modestringoptional
  • external_idstringoptionalmax 200 chars
  • metadataobjectoptional

    Arbitrary key/value map; merge-on-write (§6).

Returns

  • 200The upserted (already-existing) deck.
  • 201The newly created deck.

Failures use the standard error envelope with a closed set of codes.