Select Snapchat profile
Complete the Snapchat connection flow by saving the selected Public Profile. Snapchat requires a Public Profile to publish content. Use X-Connect-Token if connecting via API key.
API key authentication - use your Zernio API key as a Bearer token
In: header
Header Parameters
Short-lived connect token from the OAuth redirect (for API users)
Your Zernio profile ID
The selected Snapchat Public Profile
Temporary Snapchat access token from OAuth
User profile data from OAuth redirect
Snapchat refresh token (if available)
Token expiration time in seconds
Custom redirect URL after connection completes
uriResponse Body
application/json
application/json
application/json
application/json
import Zernio from '@zernio/node';const zernio = new Zernio({ apiKey: process.env.ZERNIO_API_KEY });const { data } = await zernio.connect.snapchat.selectSnapchatProfile({ body: { profileId: 'profile_abc123', selectedPublicProfile: { id: 'abc123', display_name: 'Example', }, tempToken: 'tok_abc123', userProfile: {}, },});console.log(data);{
"message": "Snapchat connected successfully with public profile",
"redirect_url": "https://yourdomain.com/integrations/callback?connected=snapchat&profileId=507f1f77bcf86cd799439011&publicProfile=My+Brand",
"account": {
"accountId": "64e1f0a9e2b5af0012ab34cd",
"platform": "snapchat",
"username": "mybrand",
"displayName": "My Brand",
"profilePicture": "https://cf-st.sc-cdn.net/...",
"isActive": true,
"publicProfileName": "My Brand"
}
}{
"error": "Missing required fields"
}{
"error": "Unauthorized"
}{
"error": "Forbidden"
}List Snapchat profiles GET
For headless flows. Returns Snapchat Public Profiles the user can post to. Use X-Connect-Token from the redirect URL.
Configure TikTok Ads Brand Identity PATCH
Set or update the Brand Identity (display name + avatar) for a `tiktokads` SocialAccount. TikTok requires every ad to carry an `identity_id + identity_type` pair. The Brand Identity is the CUSTOMIZED_USER alternative to attributing ads to a real @username (TT_USER). This route uploads the supplied image to TikTok, creates the identity via `/v2/identity/create/`, and caches the resulting `identity_id` on the account so subsequent `POST /v1/ads/create` calls can opt into it via `identityType: 'CUSTOMIZED_USER'`. Configurable on every `tiktokads` account, including linked-mode ones (those with a posting account on the same profile). Configuration is idempotent and harmless when posting is also connected: the default ad-create path still prefers TT_USER, and CUSTOMIZED_USER is only used per-ad when the caller explicitly opts in. TikTok identities are immutable post-creation. Re-saving creates a new identity on TikTok and swaps the cached id; the old identity stays orphaned on TikTok's side (harmless, no billing impact). Alternative: pass `brandIdentity` directly on `POST /v1/ads/create` to configure on first ad creation in a single round-trip.