---
title: "POST /v2/content/switch-channel-id"
method: POST
path: "/v2/content/switch-channel-id"
tags: ["v2"]
---

# POST /v2/content/switch-channel-id

`POST /v2/content/switch-channel-id`

## Request

- Base URL: `https://api.inside.ad/api`
- URL: `https://api.inside.ad/api/v2/content/switch-channel-id`
- Auth: one of:
  - OAuth 2 (authorization code, authorization URL `https://api.inside.ad/api/oauth/authorize`, token URL `https://api.inside.ad/api/oauth/token`, scopes: `content:write`)
  - API key in header `authorization`

Telegram-only maintenance operation: migrates content rows from a positive channelId to the corresponding negative (-100...) channelId, once ownership is verified. Not part of normal posting — only use if explicitly asked to fix a channelId mismatch.

## Query parameters

- `userId` number, required

## Request body

- object
  - `channelId` string, required: The (positive or negative) Telegram channelId to normalize

## Response `200`

Default Response

- object
  - `success` boolean
  - `sourceChannelId` string
  - `targetChannelId` string
  - `updatedContent` number

---

[API](https://skmtc.dev/inside/apis/inside-ad-api-documentation-v2-ai-optimized.md) · [All operations](https://skmtc.dev/inside/apis/inside-ad-api-documentation-v2-ai-optimized/llms.txt) · [OpenAPI document](https://skmtc.dev/inside/apis/inside-ad-api-documentation-v2-ai-optimized/revisions/79912b433f7f?raw)