---
title: "Register a custom destination"
method: POST
path: "/org/destinations"
tags: ["Destinations"]
---

# Register a custom destination

`POST /org/destinations`

## Request

- Base URL: `https://apiv2.senso.ai/api/v1`
- URL: `https://apiv2.senso.ai/api/v1/org/destinations`
- Auth: API key in header `X-API-Key`

Registers a custom `citeables` domain as a publishing destination for your organization and selects it for generation. Only `type: citeables` is supported. If your org already has a destination for the same domain, that existing destination is returned (with `200`) instead of creating a duplicate.

## Request body

- AddOrgDestinationRequest
  - `type` 'citeables', required: The destination type. Only `citeables` is supported.
  - `name` string, required: A display name for the destination.
  - `domain` string, required: The custom domain to register (e.g. `blog.example.com`).

## Response `200`

The existing destination for this domain (idempotent reuse).

- OrgDestinationResponse: A publishing destination available to the organization, with its per-org stats.
  - `publisher_id` string, uuid, required
  - `scope` 'shared' | 'org', required: `shared` for a globally-seeded destination, `org` for one your organization registered.
  - `type` string, required: The destination type. Currently always `citeables`.
  - `name` string, required
  - `slug` string, required
  - `display_url` string, required: The destination's display URL (its domain).
  - `live_count` integer, required: Count of your org's content currently live on this destination.
  - `last_publish_at` string, date-time: The latest publish among your org's content currently live on this destination, if any (absent once nothing is live).
  - `selected_for_generation` boolean, required: Whether this destination is currently selected as a content-generation target.

## Other responses

- `201`: The newly registered destination (stats fields start at zero/absent).
- `400`: The request was malformed — a bad path/query parameter or an invalid value.
- `401`: Missing or invalid credentials — supply a valid org API key in the `X-API-Key` header.
- `422`: The request was well-formed but cannot be fulfilled given the current state (e.g. insufficient data to act on).
- `502`: An upstream dependency failed or rejected the request.

---

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