YouTube New Video Notifications
Get a webhook when the YouTube channel of a profile uploads a video or changes the title or description of one, usually within minutes. It uses YouTube's own push notifications (PubSubHubbub), so there is nothing to poll and it does not spend your daily YouTube allowance.
YouTube does not push comments: for comments keep using comments.
These notifications are not generally available yet. Until they are, GET, POST and DELETE /api/uploadposts/youtube/push answer 503 Service Unavailable with error_code: "youtube_feature_disabled", and the youtube_video_published / youtube_video_updated events are not accepted in webhook_events.
1. Ask for the events in your webhook
Add youtube_video_published and/or youtube_video_updated to webhook_events of your account webhook (POST /api/uploadposts/users/notifications) or of the profile webhook (POST /api/uploadposts/users/profile-webhook). They are opt-in: an empty webhook_events does not turn them on.
2. Turn notifications on for the channel
POST /api/uploadposts/youtube/push
| Field | Description |
|---|---|
user | Profile username with a YouTube channel connected. |
curl -X POST https://api.upload-post.com/api/uploadposts/youtube/push \
-H 'Authorization: Apikey your-api-key-here' -H 'Content-Type: application/json' \
-d '{"user": "my-profile"}'
{
"success": true,
"message": "Subscription requested. Google confirms it within a few minutes.",
"push": {"channel_id": "UCxxxxxxxxxxxxxxxxxxxxxx", "state": "pending", "created_at": "2026-11-14T10:00:00+00:00",
"verified_at": null, "expires_at": null, "last_notification_at": null,
"events": ["youtube_video_published", "youtube_video_updated"]}
}
state moves to active once Google confirms it. Upload-Post renews it before it expires for as long as the channel stays connected and a webhook asks for the events.
GET /api/uploadposts/youtube/push?user=my-profileshows the current state (pushisnullwhen it is off).DELETE /api/uploadposts/youtube/pushwith{"user": "my-profile"}turns it off.
Notifications stop on their own when you disconnect the channel, delete the profile or the account, or remove the events from every webhook.
Webhook payload
{
"event": "youtube_video_published",
"user_email": "[email protected]",
"profile_username": "my-profile",
"platform": "youtube",
"account_id": "UCxxxxxxxxxxxxxxxxxxxxxx",
"video": {
"id": "dQw4w9WgXcQ",
"title": "My new video",
"url": "https://www.youtube.com/watch?v=dQw4w9WgXcQ",
"published_at": "2026-11-14T10:00:00+00:00",
"updated_at": "2026-11-14T10:00:05.123456789+00:00"
},
"channel": {"id": "UCxxxxxxxxxxxxxxxxxxxxxx", "name": "My channel", "url": "https://www.youtube.com/channel/UCxxxxxxxxxxxxxxxxxxxxxx"},
"created_at": "2026-11-14T10:00:07.000000"
}
youtube_video_published: the first notice of a video published after notifications were turned on (sent once per video).youtube_video_updated: any later notice for a video: title or description changes, or YouTube re-sending it.- YouTube decides what it notifies: private videos may not be notified, and it can send the same change more than once. Deduplicate by
video.id+video.updated_at. - Signed and retried like every other webhook (see Webhooks).
Errors
error_code | Meaning |
|---|---|
youtube_push_no_webhook | No webhook lists youtube_video_published or youtube_video_updated. |
youtube_push_limit | The account reached the maximum number of channels with notifications. |
youtube_push_capacity, youtube_push_unavailable, youtube_feature_disabled | Not available right now: try again later. |
youtube_push_hub_error | Google did not accept the request: retry in a few minutes. |
youtube_push_conflict (409) | Two requests for the same channel crossed: retry in a moment. |
youtube_not_connected, youtube_reauth_required | Connect or reconnect the YouTube channel. |