---
title: "Connect a Snapchat Ads pixel"
method: POST
path: "/v1/connect/snapchat-ads/credentials"
tags: ["Connect"]
---

# Connect a Snapchat Ads pixel

`POST /v1/connect/snapchat-ads/credentials`

## Request

- Base URL: `https://zernio.com/api`
- URL: `https://zernio.com/api/v1/connect/snapchat-ads/credentials`
- Auth: HTTP bearer

Connect a Snap Pixel with its Pixel ID and a Conversions API token generated in Snapchat Ads Manager (Business Details, Conversions API Tokens, visible to Organization Admins).

Zernio checks the token against the pixel on Snap's validate endpoint before saving it. The account then receives the conversion events you forward to it (`POST /v1/events`, forwarding rules). Connecting the same pixel again replaces its token.

Requires the Ads add-on.

## Request body

- object
  - `accessToken` string, required: Conversions API token from the organization that owns the pixel.
  - `pixelId` string, required: Snap Pixel ID from Events Manager, a UUID.
  - `name` string: Optional display name for the account.
  - `profileId` string, required: Your Zernio profile ID
  - `state` string: Optional state passthrough for the connect flow.
  - `redirect_url` string: Optional URL to redirect to after a successful connection, echoed back as redirectUrl.

## Response `200`

Snapchat Ads pixel connected

- object
  - `accountId` string
  - `pixelId` string
  - `accountName` string
  - `redirectUrl` string

## Other responses

- `400`: Invalid request
- `401`: Unauthorized, or Snapchat did not accept the Conversions API token for this pixel (code invalid_credentials).
- `402`: Payment method or enterprise contract required: the authenticated account hit a billing gate before the connection could proceed. Switch on `reason` to render the right prompt: - `free_tier_exceeded`: the team has connected more accounts than the free tier allows. Add a payment method to continue (billed per additional connected account). - `twitter_passthrough`: connecting an X account requires a card on file, even the 1st one, because X API calls are passed through per call. Prepaid-balance accounts never get it: they pay X calls from the balance. - `enterprise_required`: the team's enterprise contract sets a connected-account cap and it has been reached. Self-service teams have NO cap (the $1/account rate continues at any scale). The user already has a card on file; this gate is about contract terms. - `card_verification_required`: the card on file was flagged at add time (prepaid, or issued in a different country than the billing address). A one-time verification charge of `details.verification_amount_cents` (USD) is pending; it is credited to the team's usage balance, not a fee. **What to do:** redirect the end-user to `dashboard_url`. - `free_tier_exceeded`, `twitter_passthrough`, `card_verification_required`: it opens the Zernio billing page (the add-payment-method drawer, or the verification step). The request succeeds once the card is on file (or verified, or paid). - `enterprise_required`: it opens the enterprise contact form (not the billing tab), to adjust the contract's limit.
- `403`: Ads add-on required.
- `502`: Snapchat could not confirm the token right now, so nothing was saved (code platform_api_error). Retry in a minute.

## Changes

- **2026-11-18** `aa3b8109573e`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/zernio/apis/zernio-api/changes/v1/connect/snapchat-ads/credentials/post.md)

---

[API](https://skmtc.dev/zernio/apis/zernio-api.md) - [All operations](https://skmtc.dev/zernio/apis/zernio-api/llms.txt) - [OpenAPI document](https://skmtc.dev/zernio/apis/zernio-api/revisions/f57e57199cca?raw)
