These are the questions developers ask us most often when building on the Storrito API. For an overview of what the API does and how to authenticate, start with Storrito API: Schedule Instagram Stories Programmatically.
No. The API uses the same usage-based pricing as the rest of Storrito — the per-account connection fee, the storage fee, and the per-post charges for TikTok, YouTube Shorts, and Facebook Reels/Stories. There's no separate API fee. See How Storrito Credits And Pricing Work for the current rates.
Not at the moment. Once a Story posts, status-instagram-story returns the storyPostUuid and the status, but not the published Instagram Story URL or Instagram media ID. Storrito doesn't store the Instagram Story post ID yet, and there's no webhook field or separate endpoint that returns it. It's on our roadmap, but we can't promise a timeline.
Yes, with create-draft. It creates the Story media without scheduling it, so nothing posts until someone schedules it from the Storrito app. It's limited to 100 drafts per day per organization.
Pass an optional folderName to land the draft in a specific Gallery folder, for example "Upcoming Shows". Storrito creates the folder for you if it doesn't exist yet. Folders have to be top-level; nested subfolders aren't supported through the API yet.
Once a draft is in the Gallery, review and schedule it the same way as any uploaded asset: open it from the Gallery and choose Social schedule.
If you'd rather skip the review step, schedule-instagram-story still posts or schedules directly. You can also schedule far in the future (for example, 6 months out), review the Story in the Storrito editor, then reschedule it to the time you actually want it to go live.
Yes. A scheduled Story can be opened in the Storrito editor any time before it posts, so you can adjust stickers, swap the image, and change text, then reschedule it to a different time or cancel it. That's what makes the far-future scheduling above a workable stand-in for drafts.
No, not yet. The in-app Post and Schedule flow includes crossposting to Facebook, but schedule-instagram-story has no Facebook or crosspost parameter, so Stories posted through the API go to Instagram only.
You design Stories with Story Components: plain HTML and CSS that Storrito converts into a native Instagram Story with native stickers. Because it's standard HTML and CSS, you lay everything out yourself, and the text adapts to the space available. See the Story Components reference in the API documentation for examples.
A fast way to get started is to point an AI coding agent like Claude Code at that reference and ask it to build an example HTML file for you.
A Story that posts fine manually but gets stuck on “retrying” through the API usually points to a problem with the HTML you're sending. Compare your markup against the examples in the Story Components reference and match that format.
Storrito doesn't produce a standalone preview image through the API yet. As a workaround, since you design Stories as HTML and CSS with Story Components, you can render that HTML page and capture a screenshot with a headless browser service such as Browserbase. An AI coding agent like Claude Code can wire this up for you.
If you have a question that isn't covered here, reach out to support and we'll help with your integration.