Sign in
customer cabinet

Photo

Changed on

One photo from the customer's own cabinet, for the customer's own live session.

A photo is not behind an address anyone can open: the browser asks with the session it earned (the same proof every cabinet call carries), and three things must all hold on every load: the session is live (not revoked, not expired, contact still verified), a cabinet file of THIS customer names the photo, and the artifact is an image. Anything else is the same 404, so a guess learns nothing. The bytes come through the backend, never as a bucket address.

post/v1/portal/photos

Request

  • Base URL: https://api.stormy.ai (the document declares no server; this is the origin it was published from)
  • URL: https://api.stormy.ai/v1/portal/photos
  • Auth: none declared

Request body

session_tokenstring required
event_keystring
artifact_idstring uuid required

Response

Successful Response

unknown required

Changes