Adsapi Snapchat Snapchat Marketing API

Name: Snapchat Marketing API
Brand: Snapchat Marketing API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentMarketingAdvertisingoauth2114 EndpointsREST

For Agents

Manage Snapchat ad accounts, campaigns, ad squads, creatives, audiences, pixels, custom conversions, and product catalogs through OAuth 2.0.

Install Jentic One Beta

Connect the Snapchat Marketing API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Snapchat Marketing API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Snapchat Marketing API.

List and manage organisations, ad accounts, members, and roles for Snapchat advertising

Create and update campaigns, ad squads, ads, and creatives across an ad account

Build and update custom audience segments and saved targeting profiles

GET STARTED

Start building with Snapchat Marketing API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Snapchat Marketing API for, with concrete tasks.

★ Snapchat Campaign Launch and Management

Performance marketing teams launch and manage Snapchat campaigns end-to-end via the Campaigns, AdSquads, Ads, and Creatives endpoints. The hierarchy mirrors Snapchat's UI so teams can replicate manual campaign builds in code, including budget caps, scheduling, and creative attachments. This is the foundation for cross-channel ad ops platforms that include Snapchat.

Create a campaign under ad account 999, attach an ad squad with $50/day budget, and launch an ad with creative ID 4421

Custom Audiences and Targeting

Audience teams sync first-party customer lists into Snapchat as custom audience segments using the Segments endpoints, then attach them to ad squads through the Targeting endpoints. Saved targeting profiles can be reused across campaigns to enforce consistent audience definitions.

Update segment 7782 with the latest 50,000 hashed emails from the CRM via the segments endpoints

Conversion Tracking with Pixels and Custom Conversions

Measurement teams configure Snapchat Pixels and custom conversions through the Pixels and CustomConversions endpoints to track on-site events back to ad spend. This is required for ROAS calculations and bid optimisation that uses conversion signals rather than only clicks.

Create a custom conversion for 'add_to_cart' on Pixel 5511 via the custom conversions endpoints and verify events are firing

Dynamic Product Ads via Catalogs

E-commerce advertisers run dynamic product ads on Snapchat by maintaining a Catalog with one or more ProductFeeds and ProductSets. The Catalogs, ProductFeeds, and ProductSets endpoints expose feed scheduling, set rules, and catalog membership so a feed pipeline can be wired up entirely via API.

Create a catalog, attach a product feed pointing at the storefront's CSV URL, and define a product set for the SS26 collection

Agent-Driven Snapchat Ad Ops via Jentic

AI agents can run Snapchat campaign and audience operations through Jentic without orchestrating the full OAuth 2.0 dance themselves. Jentic stores the OAuth credentials in the vault and intent search resolves to the right endpoint among 114, so the agent does not need to read the full marketing-api docs to operate effectively.

Search Jentic for 'list snapchat campaigns', load GET /adaccounts/{ad_account_id}/campaigns, and execute it for ad_account_id 999

Key Endpoints

114 endpoints — jentic publishes the only available openapi specification for the snapchat marketing api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/me/organizations

List the user's organisations

GET

/organizations/{organization_id}/adaccounts

List ad accounts in an organisation

GET

/adaccounts/{ad_account_id}/campaigns

List campaigns in an ad account

GET

/adaccounts/{ad_account_id}/adsquads

List ad squads in an ad account

GET

/campaigns/{campaign_id}

Get a campaign by ID

GET

/organizations/{organization_id}/fundingsources

List funding sources

GET

/me/organizations

List the user's organisations

GET

/organizations/{organization_id}/adaccounts

List ad accounts in an organisation

GET

/adaccounts/{ad_account_id}/campaigns

List campaigns in an ad account

GET

/adaccounts/{ad_account_id}/adsquads

List ad squads in an ad account

GET

/campaigns/{campaign_id}

Get a campaign by ID

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Your Snapchat OAuth client secret, access token, and refresh token are stored once, encrypted, by your own Jentic One instance, which refreshes tokens automatically at execution time. The raw credentials never enter the agent's prompt, logs, or context.

Intent-based discovery

Agents search Jentic by intent such as 'list snapchat campaigns' or 'read an ad account's funding sources', and Jentic returns the matching Snapchat operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

Time to first call

FAQs

Specific to using Snapchat Marketing API through Jentic.

Why is there no official OpenAPI spec for the Snapchat Marketing API?

Snap publishes documentation at developers.snap.com/api/marketing-api but does not ship an OpenAPI specification. Jentic generates and maintains this spec from the published developer portal so AI agents and developers can call it via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

What authentication does the Snapchat Marketing API use?

The API uses OAuth 2.0. You register an app in the Snap Business Manager, run the OAuth authorisation code flow to get an access token and refresh token, and send the access token in the Authorization header. Through Jentic, the OAuth credentials and refresh tokens are held in the vault so the agent never handles them.

Can I create custom audiences with the Snapchat Marketing API?

Yes. The Segments endpoints under /adaccounts/{ad_account_id}/segments let you create and update custom audiences from hashed customer lists, and the Targeting endpoints attach them to ad squads.

How do I list campaigns in an ad account through Jentic?

Search Jentic for 'list snapchat campaigns', load GET /adaccounts/{ad_account_id}/campaigns, and execute it with the ad_account_id. Jentic returns the input schema so the agent supplies only the parameters Snapchat accepts.

What are the rate limits for the Snapchat Marketing API?

Snap enforces per-app and per-account rate limits documented in the Snap developer portal but not in the OpenAPI spec. Expect HTTP 429 responses if you exceed them and retry with exponential backoff. Through Jentic, retries with backoff can be configured in the execution request.

Can I operate product catalogs for dynamic ads with the Snapchat Marketing API?

Yes. Catalogs, ProductFeeds, and ProductSets endpoints together model the dynamic-ad inputs: a catalog holds one or more product feeds and product sets define the slices used in ads.

Can I limit what my agent is allowed to do with the Snapchat Marketing API?

Yes. Because you run Jentic One yourself, your own rules decide which operations and credentials the agent may use. Since Snapchat puts the ad account ID in the URL path (/adaccounts/{ad_account_id}/...), you can pin the agent to a single ad account so it lists only that account's campaigns and ad squads and touches nothing else. You choose exactly which endpoints it may call, so write operations like creating campaigns or updating segments stay off unless you grant them.