Skip to main content
POST
Keep reels in the creator's Swipe file, their own reference list, only when the creator asks, as a double tap on any reel in a Dally player does; a note keeps their words verbatim; a reel already there changes nothing. A reel is kept when this answers kept, not before; the word is keep, since saves is Instagram's own count on a reel.

Authorizations

Authorization
string
header
required

A WorkOS-dashboard-issued internal API key on Authorization: Bearer.

Body

application/json
reels
object[]
required

The reels this call is about, one to 60; the same reel twice counts once.

Required array length: 1 - 60 elements
note
string

The creator's reason in their own words, verbatim, when they gave one: from "keep the second one for the hook" the note is "for the hook", never the instruction to keep. Recorded on the fact for every reel in this call exactly as sent, spaces included.

Required string length: 1 - 500
request_id
string

The Dally request id of the canvas the reels were shown on, when known, so the Swipe file remembers where a reel came from.

Required string length: 1 - 200
idempotency_key
string

The caller's key for this one call; a retry with the same key replays the answer instead of acting twice. Absent, this request's id serves.

Required string length: 1 - 200
source
enum<string>

frame when the person acted in a Dally player, chat when the model did; chat when absent.

Available options:
frame,
chat

Response

Success. request_id is present on every response.

marks
object[]
required

One mark per reel sent, in the order sent.

show
object
required

How it is shown: dally_write renders the Swipe file on this very answer, so the creator already sees the kept reel; do not render it again. The file reads itself and takes no rows from you.

request_id
string
required

Server-minted id for this request. Present on every response, success and error — quote it when reporting a problem.

Minimum string length: 1