Destination · publishing reference
Snapchat publishing reference for Postdom
This Snapchat publishing reference explains the Public Profile prerequisite, current story surface, Spotlight-sourced limits, omitted settings, and outcome boundary.
Human authorization boundary
Snapchat publishing reference connection requirements
A human completes the destination connection. The agent receives the resulting account ID—not the social credential—and supplies that exact account ID to publish_video.
connectionOAuth
prerequisiteSnapchat needs a Public Profile on your account - you will choose one while connecting. Regular accounts cannot publish.
current source surfacestory
Configured output
What Postdom sends to Snapchat
The public tool accepts product-level publishing fields. Postdom builds destination settings after validation; callers cannot smuggle an undocumented settings object through publish_video.
settings- omitted
Postdom does not send locale or skip_save_to_profile.
Postdom sends no Snapchat-specific settings. The current core surface is story, so this page does not claim every request becomes a live Spotlight.
{
"platform": "snapchat",
"settings": {}
}Enforced, documented, or unknown
Snapchat publishing limits
Every row comes from the current @postdom/core registry. “Postdom enforced” means the source contract checks the fact. A recommendation, documented-but-unenforced fact, or unpublished value must not be presented as a passed validation.
caption max chars
4000
Postdom contract · verified 2026-08-21T00:00:00.000Z
Evidence reference retained in the core registry.
media max bytes
524,288,000 bytes
Postdom contract · verified 2026-08-21T00:00:00.000Z
Evidence reference retained in the core registry.
video max seconds
600
Postdom contract · verified 2026-08-21T00:00:00.000Z
Evidence reference retained in the core registry.
video mime types
video/mp4, video/quicktime
Postdom contract · verified 2026-08-21T00:00:00.000Z
Evidence reference retained in the core registry.
image mime types
image/jpeg, image/png, image/gif, image/webp
Postdom contract · verified 2026-08-21T00:00:00.000Z
Evidence reference retained in the core registry.
public profile spotlight description
160
Unit: characters · Field: description · Scope: Public Profile API - Spotlight
Platform evidence · verified 2026-09-02T00:00:00.000Z
Official sourcevideo min seconds
6
Platform evidence · verified 2026-09-02T00:00:00.000Z
Official sourcevideo max seconds
60
Platform evidence · verified 2026-09-02T00:00:00.000Z
Official sourcevideo mime types
video/mp4
Platform evidence · verified 2026-09-02T00:00:00.000Z
Official sourceresolution min pixels
width: 540; height: 960
Platform evidence · verified 2026-09-02T00:00:00.000Z
Official sourceaspect ratio
Not published
Platform evidence · verified 2026-09-02T00:00:00.000Z
Official sourceresolution max pixels
Not published
Platform evidence · verified 2026-09-02T00:00:00.000Z
Official sourcevideo max bytes
1,000,000,000 bytes
Platform evidence · verified 2026-09-02T00:00:00.000Z
Qualification
Snap's own figure - "A file of upto 1 GB can be uploaded through the multipart upload API" - but scoped to the upload mechanism rather than to Spotlight, and an order of magnitude above Postdom's 500 MB global cap. No request Postdom accepts can reach it, so a gate here would be unreachable and a violation test for it would pass on the global rule while proving nothing about Snapchat. Decimal rather than binary: the source says "1 GB" in prose with no convention stated, and the decimal reading is the smaller one, which is the safe error for a maximum. Reclassify the day the global cap rises above it.
Result boundary
How to verify the Snapchat outcome
The limit evidence comes from Snapchat's Spotlight API, while Postdom's current source surface remains story. No live Spotlight, locale choice, or saved-profile result has been observed here.
Never collapse a workflow state into success
Store the Postdom post ID, read the exact destination state with get_publish, and preserve a missing public URL, approval state, terminal refusal, or provider error exactly as returned.
Nine modeled fields
Snapchat metric availability
The matrix records evidence states, not guaranteed live values. Unverified and never remain null with a reason; zero remains a measured zero.
viewsViewsRequired view count in a normalized snapshot.
Not verified
Always null with an explicit reason.
likesLikesRequired like count in a normalized snapshot.
Not verified
Always null with an explicit reason.
commentsCommentsRequired comment count in a normalized snapshot.
Not verified
Always null with an explicit reason.
sharesSharesRequired share count in a normalized snapshot.
Not verified
Always null with an explicit reason.
savesSavesNullable saved or favorited count.
Not verified
Always null with an explicit reason.
watch_time_sWatch timeNullable total watch time in seconds.
Not verified
Always null with an explicit reason.
avg_watch_pctAverage watchNullable average watched percentage.
Not verified
Always null with an explicit reason.
completion_pctCompletionNullable completion percentage.
Not verified
Always null with an explicit reason.
follower_deltaFollower deltaNullable follower-change field.
Not verified
Always null with an explicit reason.
Verification scope
Snapchat evidence boundary
Contract evidence is not an observed publication
These pages describe source-backed product contracts. They do not represent an authenticated end-to-end publication or analytics test.
Inspect the connected tool schema before acting. Current source may be ahead of the separately published @postdom/mcp helper.
Use the contract
Publish with explicit authority and outcomes
Create a workspace, connect an eligible account, and let the agent use only the fields exposed by the connected schema.