Snapchat API

Snapchat API for posting and scheduling Public Profile content workflows

A Snapchat API for Public Profile metadata, Stories, Spotlights, and creator metrics, kept beside the rest of your social stack.

Build Snapchat Public Profile workflows for creator discovery, content management, Stories, Saved Stories, Spotlights, and campaign reporting context.

Last updated: July 2026

View API docs

One API key. No per-account fees. 15 platforms.

Public ProfilesContent ManagementCreator Discovery

Quick start

API request

1await fetch("https://api.bundle.social/api/v1/post", {2  method: "POST",3  headers: {4    "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY,5    "Content-Type": "application/json"6  },7  body: JSON.stringify({8    teamId: "team_123",9    title: "Snapchat Public Profile launch",10    postDate: "2026-05-14T10:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["SNAPCHAT"],13    data: {14      SNAPCHAT: {15        type: "STORY",16        text: "New drop is live.",17        uploadIds: ["upload_vertical_video"]18      }19    }20  })21});

Official APIs500k+ connected accountsDirect engineer support

Building directly on Snap Kit and Snapchat APIs

Snapchat workflows are camera-first, mobile-native, and different from feed-based publishing.

Public Profile workflows combine metadata, metrics, creator discovery, and content management instead of a single generic post object.

Teams evaluating Snapchat usually need it beside Instagram, TikTok, and YouTube Shorts, not as a disconnected tool.

What bundle.social handles

Keep Snapchat planning close to existing publishing, scheduling, media, and analytics workflows.

Use Public Profile context to connect creator discovery, campaign content, and reporting in one product surface.

Track Story-ready media, account eligibility, and campaign timing beside other visual channels.

Snapchat support for camera-first content operations

Snapchat's Public Profile API centers on profile metadata, public metrics, creator discovery, and content management. bundle.social keeps those camera-first assets and publishing workflows near the rest of your social stack.

Workflow

How it works

Connect accounts once, then create and schedule posts with channel-specific fields from one API.

Create an API key

Generate an organization API key in the dashboard and use it with the x-api-key header.

Connect accounts

Connect each social account once. bundle.social keeps the account mapping ready for future posts.

We publish to the public profile surface

Snapchat Stories and Spotlight have separate media requirements and both need a public profile on the connected account. You send one request; bundle.social targets the right surface and validates media before upload.

Product architecture

Build social media workflows without rebuilding every platform

Snapchat API for Public Profiles, Stories, and creator workflows

A Snapchat API integration is different from a feed-first social post. Product teams need Public Profile context, creator discovery, Story behavior, Saved Stories, Spotlights, Lenses, account eligibility, app review, and permission-aware metrics. If these pieces are treated as a generic caption and media upload, Snapchat becomes a separate product surface instead of a reliable campaign workflow.

bundle.social brings Snapchat into the same publishing and planning layer used for the rest of your social stack. Your product can keep camera-first assets, Story-ready media, creator context, scheduling intent, and status tracking close to the same account, media, and reporting model your team already uses for other visual channels.

Public Profile data and content management belong together

Snapchat Public Profile workflows need more than a post payload. The useful product decisions include profile category, tier, verification state, OAuth state, data-sharing access, public metrics, audience insights, and whether the workflow is about discovery, publishing, or campaign reporting. Those decisions shape what a brand, creator tool, or agency can safely expose to users.

With bundle.social, Snapchat-specific context stays inside the platform workflow while the surrounding account, media, scheduling, and status model remains shared. That lets SaaS products, creator platforms, and agencies build Snapchat workflows without sacrificing cross-platform consistency.

Snapchat reporting connected to the campaign pipeline

Teams using Snapchat care about what happens after content goes live: profile metrics, Story performance, creator fit, campaign timing, and how Snapchat activity compares with Instagram, TikTok, YouTube Shorts, and other visual channels. Reporting is easier when the profile, account, content, and campaign that produced the data remain connected.

bundle.social keeps Snapchat planning and available performance context close to post history, scheduled campaigns, media uploads, and cross-platform reporting. That gives products a stronger foundation for customer dashboards, agency reports, and AI workflows that need creator and content data after a campaign ships.

Capabilities

Snapchat API workflows for Public Profiles

Public Profile metadata, Story-ready creative, Saved Stories, Spotlights, campaign timing, and status tracking for teams that need Snapchat beside other visual channels.

Public Profile context

Retrieve metadata and statistics for Snapchat Public Profiles, then keep that context close to campaign planning and reporting workflows.

Creator Discovery support

Use public metrics and opted-in audience insights to evaluate creator fit before pairing Snapchat with a broader launch plan.

Content Management workflows

Plan Story, Saved Story, Spotlight, and Lens workflows around media readiness, account permissions, and campaign timing.

API key authentication

Use one bundle.social API key for server-to-server requests while connected accounts and native platform permissions stay controlled.

Status and reporting context

Keep Snapchat content state, creator context, and performance signals beside the rest of your social API workflow.

Platform specifics

Snapchat Public Profile workflows need their own shape

Snapchat should not be treated like another text caption destination. The useful workflow starts from Public Profiles, camera-first assets, Story behavior, and creator or brand campaign timing.

Creator Discovery

Snapchat Public Profile data helps teams evaluate creators, public metrics, and opted-in audience insights before a campaign starts.

Content Management

Stories, Saved Stories, Spotlights, and Lenses each need media readiness and permission-aware workflow design.

Public Profile tiers

Profile category, tier, verification state, and OAuth/data-sharing access affect which details and metrics a workflow can use.

Developer example

Schedule a Snapchat post

Examples use bundle.social's public API shape: API key authentication, a post date, selected social account types, and platform-specific data.

TypeScript

API request

1await fetch("https://api.bundle.social/api/v1/post", {2  method: "POST",3  headers: {4    "x-api-key": process.env.BUNDLE_SOCIAL_API_KEY,5    "Content-Type": "application/json"6  },7  body: JSON.stringify({8    teamId: "team_123",9    title: "Snapchat Public Profile launch",10    postDate: "2026-05-14T10:00:00.000Z",11    status: "SCHEDULED",12    socialAccountTypes: ["SNAPCHAT"],13    data: {14      SNAPCHAT: {15        type: "STORY",16        text: "New drop is live.",17        uploadIds: ["upload_vertical_video"]18      }19    }20  })21});

Supported content

Public ProfilesStoriesSaved StoriesSpotlightsLensesCreator metrics

Honest limitations

Snapchat workflows depend on Snap account eligibility, app review, permissions, and Public Profile access.
Available content and metrics vary by Public Profile category, tier, OAuth state, and data-sharing permissions.

Guarantees

Developer-first infrastructure

Visible post status

Track scheduled, processing, posted, retrying, and error states per post.

Verbose errors

When native APIs fail, we return human-readable error messages and actionable recovery steps.

Flat pricing

No per-post counting. Predictable pricing for teams managing many users, workspaces, and connected accounts.

Same-day support

Direct access to the engineers building the API. We respond to technical issues the same day, sometimes the same hour.

FAQ

Questions developers ask before building

What does a Snapchat integration require on the account side?

A public profile on the connected account. Story and Spotlight publishing both depend on it, and available profile, content, and metrics reads vary by category, tier, OAuth state, and data-sharing permissions.

Are Stories and Spotlight the same publishing surface?

No. They have separate media requirements, so validating media against the intended surface before upload avoids a failed transfer rather than a failed request.

What can we read back from Snapchat?

Public profile and analytics reads, subject to the permissions the account has actually granted. Treat metric availability as variable and delivery state as the dependable signal.

Does this replace Snap Kit and Snapchat APIs?

No. bundle.social calls Snap Kit and Snapchat APIs for you and absorbs the work around it: token storage and refresh, media handling, scheduling, status transitions, and turning platform errors into a cause and a next action.

Are Snapchat analytics available through the API?

Snapchat analytics are limited or unavailable through the native API, so post status and delivery state are the reliable signals to build on.

Snapchat Scheduler

See the Snapchat planning page.

Snapchat Story API

Build Story-first campaign workflows.

TikTok API

Current short-form video publishing workflows.

Instagram API

Current visual publishing workflows.