RivermarkRivermark
API reference

GET and DELETE /design/{id}

Retrieve design metadata, and remove designs permanently.

Manage existing designs — including brand kits, which are designs internally. All operations address the design by its persistent rmd_… ID.

Retrieve a design

Endpoint
GET https://api.rivermark.ai/design/{id}
cURL
curl https://api.rivermark.ai/design/rmd_cj4hbqz2w0003mz6x7p9q2xe \
  -H "Authorization: Bearer $RIVERMARK_API_KEY" | jq
200 OK
{
  "design_id": "rmd_cj4hbqz2w0003mz6x7p9q2xe",
  "created_at": "2026-10-12T09:24:11Z",
  "continued_from": null,
  "change_summary": "Created an Instagram post for the summer sale",
  "outputs": [{ "id": "post", "format": "png", "width": 1080, "height": 1350 }],
  "cost": 0.10
}

Prop

Type

Re-rendering

Designs are stored permanently, but rendered image URLs are temporary by design. To get fresh renders of a stored design, issue a POST /design with the design as a reference and a task like "Render the current design unchanged" — cheap, since no design work is involved. A dedicated on-demand rendering endpoint is on the roadmap.

Delete a design

Endpoint
DELETE https://api.rivermark.ai/design/{id}
cURL
curl -X DELETE https://api.rivermark.ai/design/rmd_cj4hbqz2w0003mz6x7p9q2xe \
  -H "Authorization: Bearer $RIVERMARK_API_KEY" | jq
200 OK
{
  "design_id": "rmd_cj4hbqz2w0003mz6x7p9q2xe",
  "deleted": true
}

Removes the design, its assets, and its outputs from Rivermark's servers:

  • The design becomes immediately inaccessible via the API.
  • Copies may be retained for up to 30 days for diagnostic and retention reasons, but are not accessible.
  • Deleting a design does not delete uploaded files, and does not affect designs forked from it (they are independent designs).
  • Brand kits can be deleted the same way — but note that any pipeline still referencing the ID will start failing; design references in your own database are your source of truth.

On this page