---
title: "Add an event destination"
method: POST
path: "/v1/events/destinations"
tags: ["Conversions"]
---

# Add an event destination

`POST /v1/events/destinations`

## Request

- Base URL: `https://zernio.com/api`
- URL: `https://zernio.com/api/v1/events/destinations`
- Auth: HTTP bearer

Saves an ad platform destination for a profile, so events sent to `POST /v1/events` for that profile are forwarded
to it. Pick `destinationId` from `GET /v1/accounts/{accountId}/conversion-destinations`. Set `eventNames` to forward
only those events (for example only `Purchase`); leave it out to forward every event.

## Request body

- object
  - `profileId` string, required
  - `accountId` string, required: Connected ads account ID that owns the destination.
  - `destinationId` string, required
  - `eventNames` string[]

## Response `201`

Destination saved.

- object
  - `destination` EventDestination
    - `id` string: Event destination ID, used to delete it.
    - `profileId` string
    - `accountId` string
    - `destinationId` string: Platform destination (pixel, conversion action, rule, ...).
    - `eventNames` string[], nullable: Event names forwarded to this destination; null forwards every event.
    - `createdAt` string, date-time

## Other responses

- `400`: Invalid request
- `401`: Missing or invalid API key. `code` is `missing_credentials` when no Authorization header was sent and `invalid_credentials` when the key is unknown, revoked or expired.
- `404`: Resource not found
- `409`: The profile already sends events to this destination (code `invalid_resource_state`).

## Changes

- **2026-10-26** `2ccee257b7c2`: 1 info
  - endpoint added

[Operation history](https://skmtc.dev/zernio/apis/zernio-api/changes/v1/events/destinations/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/c319eb5d95b6?raw)