---
title: "Youtube Manage Authorize"
method: GET
path: "/social/youtube/manage/authorize"
tags: ["Social"]
---

# Youtube Manage Authorize

`GET /social/youtube/manage/authorize`

## Request

- Base URL: `https://api.muapi.ai`
- URL: `https://api.muapi.ai/social/youtube/manage/authorize`
- Auth: one of:
  - API key in header `x-api-key`
  - OAuth 2 (client credentials, token URL `https://api.muapi.ai/oauth/token`)

Request youtube.force-ssl for an already-connected YouTube account.

youtube.upload (the default publish scope) covers uploading and setting
thumbnails but NOT editing title/description/tags/category/privacy after
the fact — YouTube's videos.update requires this broader scope. Kept as
its own incremental grant, same pattern as the analytics authorize/
callback pair above, rather than requested by default on every new
connection: it's a sensitive scope pending Google verification (see
docs/youtube_analytics_oauth_backlog.md), so this route is only useful
once that verification completes.

## Query parameters

- `account_id` integer, required: Existing ConnectedSocialAccount to add the metadata-edit scope to
- `redirect_to` string
- `team_id` integer, nullable

## Headers

- `x-api-key` string
- `x-embed-code` string, nullable
- `x-agent-embed-code` string, nullable
- `x-whitelabel-studio` string, nullable
- `authorization` string, nullable

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

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