> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sapt.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Send a CAPI test event

> Fire a synthetic conversion to verify the pixel + CAPI credential end-to-end. Watch for it in Meta’s Events Manager Test Events tab.



## OpenAPI

````yaml https://api.sapt.ai/openapi.json post /projects/{projectId}/capi-pixel/test-event
openapi: 3.1.0
info:
  title: Sapt Platform API
  version: 1.0.0
  description: >-
    API for Sapt platform - project management, authentication, and email
    services
servers:
  - url: https://api.sapt.ai
    description: Production
  - url: http://localhost:8787
    description: Local development
security: []
tags:
  - name: Accounts
    description: >-
      The social accounts connected to a project. Start here — the `id` of an
      account is the `socialAccountId` that every posting, scheduling and
      analytics call takes.
  - name: Actions
  - name: Ads
  - name: Agents
  - name: Analytics
    description: >-
      Account- and post-level organic performance for connected Instagram and
      Facebook accounts.
  - name: Assets
  - name: Auth
  - name: CMS
  - name: CRM
  - name: Calendar
  - name: Comments
    description: >-
      Read, reply to, hide and delete comments on published Instagram and
      Facebook posts.
  - name: Content Calendar
    description: >-
      Create, schedule, update and publish organic posts, and stage the media
      they carry. Publishing a post whose status is `failed` retries it.
  - name: Contracts
  - name: Conversions
    description: >-
      Meta server-side Conversions API (CAPI): discover pixels, connect a pixel
      + CAPI token, and send deduped server-side conversions.
  - name: Dashboard Sidebar
  - name: Emails
  - name: Engagement
    description: >-
      Act as the Page or account on published posts: comment, like, unlike, and
      delete a published post.
  - name: Geo
  - name: Google Ads
  - name: Google Analytics
  - name: Google Business
  - name: Integrations
    description: >-
      Connect third-party providers (Meta, Gmail, Google Business Profile, …).
      List providers, mint OAuth connect links, and poll connection status.
  - name: Invitations
  - name: Memory
  - name: OAuth Clients
  - name: Project Roles
  - name: Project Templates
  - name: Projects
  - name: Schedules
  - name: Service Accounts
  - name: Socials
    description: >-
      Organic social: the connected accounts, the content calendar, media
      staging, publishing, comments and engagement across Instagram, Facebook,
      TikTok, YouTube and Google Business Profile.
  - name: Team
  - name: Users
  - name: Web Analytics
  - name: Workflows
paths:
  /projects/{projectId}/capi-pixel/test-event:
    post:
      tags:
        - Conversions
      summary: Send a CAPI test event
      description: >-
        Fire a synthetic conversion to verify the pixel + CAPI credential
        end-to-end. Watch for it in Meta’s Events Manager Test Events tab.
      parameters:
        - schema:
            type: string
            format: uuid
            description: The project id.
            example: 123e4567-e89b-12d3-a456-426614174000
          required: true
          description: The project id.
          name: projectId
          in: path
      requestBody:
        required: false
        content:
          application/json:
            schema:
              type: object
              properties:
                eventName:
                  type: string
                  enum:
                    - Lead
                    - Purchase
                    - CompleteRegistration
                    - AddToCart
                    - InitiateCheckout
                    - PageView
                    - ViewContent
                    - Subscribe
                    - Qualified
                    - Schedule
                    - Contact
                    - Showed
                    - NoShow
                    - Disqualified
                  description: Event name to simulate. Defaults to `Lead`.
                testEventCode:
                  type: string
                  description: Events Manager test-event code.
                  example: TEST12345
      responses:
        '202':
          description: Test event sent
          content:
            application/json:
              schema:
                type: object
                properties:
                  eventId:
                    type: string
                  eventName:
                    type: string
                    enum:
                      - Lead
                      - Purchase
                      - CompleteRegistration
                      - AddToCart
                      - InitiateCheckout
                      - PageView
                      - ViewContent
                      - Subscribe
                      - Qualified
                      - Schedule
                      - Contact
                      - Showed
                      - NoShow
                      - Disqualified
                required:
                  - eventId
                  - eventName
        '400':
          description: Bad request
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    description: Error message
                  code:
                    type: string
                    description: Error code for programmatic handling
                required:
                  - message
        '403':
          description: Forbidden
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    description: Error message
                  code:
                    type: string
                    description: Error code for programmatic handling
                required:
                  - message
        '404':
          description: Not found
          content:
            application/json:
              schema:
                type: object
                properties:
                  message:
                    type: string
                    description: Error message
                  code:
                    type: string
                    description: Error code for programmatic handling
                required:
                  - message
      security:
        - bearerAuth: []
components:
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        JWT token obtained from /api/auth/token endpoint. Token is verified
        using JWKS and must include a valid user identifier.

````